You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it might be confusing for new-comers since there is no Collection object actually.
In reality, such methods are defined not inCollection but in the specific collection objects, e.g. List.concat or Set.empty.
I first imagined that each signatures have a note like
objectCOLLECTION {
defempty[A]:COLLECTION[A]
}
// COLLECTION could be actual collection type, like List or Set.
but this is not ideal since the signatures requires translations.
So I would suggest to add
A dedicated page regarding this simplification somewhre.
Links to the page in the functions
For methods in trait, such simplification is fine, I think !!
The text was updated successfully, but these errors were encountered:
I found using Collection object as the best way to express" the companion object of the trait Collection, where Collection means any class that behaves like that. It's complicated to keep the balance between being realistic and keeping things easy.
Anyway I agree with you that some kind of explanation need to be added.
There are some entries for methods defined in object like Collection.concat and Collection.empty.
I think it might be confusing for new-comers since there is no
Collection
object actually.In reality, such methods are defined not in
Collection
but in the specific collection objects, e.g.List.concat
orSet.empty
.I first imagined that each signatures have a note like
but this is not ideal since the signatures requires translations.
So I would suggest to add
For methods in trait, such simplification is fine, I think !!
The text was updated successfully, but these errors were encountered: