... | ... | @@ -13,15 +13,16 @@ These are features which we might want to consider for removal or replacement wi |
|
|
|
|
|
- fine control of strictness can require careful placement of these and let/where would obscure what is happening and get very verbose with nested \~ patterns.
|
|
|
- are used in several safe programing idioms that would not be workroundable.
|
|
|
- class contexts on data definitions
|
|
|
|
|
|
- For removal: they add no extra useful expressivity that is not already present in the function signatures which use the datatype.
|
|
|
- [Defaulting](defaulting)
|
|
|
- record syntax (see also [ExistingRecords](existing-records))
|
|
|
- [CompositionAsDot](composition-as-dot)
|
|
|
- the Prelude (or at least, seriously [trim it to the minimum possible](prelude))
|
|
|
- the monomorphism restriction
|
|
|
|
|
|
- (JL) This one has been worked so extensively in the past, I find it hard to imagine we could make any significant progress.
|
|
|
- classes (no really, there are people who advocate this!)
|
|
|
|
|
|
- (JL) This would so fundamentally change the nature of Haskell as to make it a different language. It is surely out of scope for what we plan to accomplish. |
|
|
- class contexts on data definitions
|
|
|
|
|
|
- For removal: they add no extra useful expressivity that is not already present in the function signatures which use the datatype.
|
|
|
- the Prelude (or at least, seriously [trim it to the minimum possible](prelude))
|
|
|
- [Defaulting](defaulting)
|
|
|
- record syntax (see also [ExistingRecords](existing-records)) |