Builders / type abbreviations for NonEmpty collections
See original GitHub issueI propose we add a builder for NonEmptySeq<_>
and type abbreviations for all 4 NonEmpty collections.
The question is, how do we call those builders / type abbreviations?
I can think of 2 options:
-
neseq
,nelist
,nemap
andneset
-
nseq
,nlist
,nmap
andnset
I think option 1 is being used in Haskell, with capital NE
.
Anyway this is F# and although it’s nice to align with other languages naming, we have different naming conventions.
Note: for the existing nel
builder we can deprecate it, or just keep it as a second abbreviation, which won’t be promoted.
Thoughts? Please, existing NonEmptyList users, chime in.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Construction Drawing Abbreviations
The following is a list of abbreviations found on a typical set of construction drawings designed to help you interpret information on your...
Read more >The Architecture of Scala Collections
Builders are generic in both the element type, Elem , and in the type, To , of collections they return. Often, a builder...
Read more >Proposal: Type aliases / abbreviations / newtype · Issue #410
F# has a feature called type abbreviations where a more complex type can have an easier to use alias. I am finding more...
Read more >Shipping-terms-and-abbreviations-1.pdf
CY:- Container Yard Collection and Distribution point for loaded FCL and empty containers. D:- Door. DAA:- Discharge always afloat.
Read more >10 Understanding Acronyms and Abbreviations
Acronym or Abbreviation Description Field Size Needed to Translate Double‑byte
A/B or AB Address Book 10
A/P Accounts Payable 8
A/R Accounts Receivable 8
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
My vote goes for
n
.So far it seems I’m the only one 😦
Thanks for the feedback,
ne
is clearly the winner, with all voices (except mine) supporting it.