Question : why hidden Gen functions?
See original GitHub issueWhy are Gen.where
, Gen.sized
(and other functions) hidden from code hints in Visual Studio using the EditorBrowsableState.never
annotation?
I rely on hints to remind me of the possibilities. Those are costly, I suppose it is the reason, but why hide them instead of adding for example a warning in the doc string?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Are you a hidden gem or are you hiding (in plain sight)?
For the purpose of this article a hidden gem is an individual who is extremely talented but is flying under the radar.
Read more >Identifying Hidden Gems on Your Team
Hidden gems are team members who have been typecast in a role but have innate characteristics ... Identifyingthe hidden gemsis critical for two...
Read more >Rethinking Potential: Should We Search for Hidden Gems ...
The key questions our clients ask about Hidden Gems are how likely it is that they exist, where they might be hiding and...
Read more >Asking Big Questions #010: "What Counts As A Hidden Gem ...
In conclusion, I believe that, in the modern world, the phrase hidden gem can be used in a personal way (to describe a...
Read more >What's an alternative for "hidden gem"?
Hidden gems is an idiom which means something which is extremely outstanding and not many people may know about; for example, Blame It...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, thanks for the idea…I was taking this as a lesson to avoid those kinds of tricks though 😉
You could use an “unspeakable” compiled name to break C#:
that would break binary compatibility, of course …