Richard Eisenberg
Richard Eisenberg
This certainly looks sensible to me, but is it worth adding a new feature to the language? I'd personally want to see a bunch more people chiming in saying "ooh...
To me, there are two separable concerns here, which we may want to debate separately. 1. Do we want immutable arrays as a first-class concept in the compiler? This means...
For what it's worth, we've been tempted to write `floatiarray`, but just haven't gotten around to it. I agree that it make sense here.
I will plan to review this next week.
Strongly in favor of this proposal as well, but can we change it to `InstanceSignatures`, please, echoing @zenzike ? Although it would be on by default, and so the only...
Yes. The "not worth the bother" part was about renaming `InstanceSigs` to `InstanceSignatures`.
This all seems hunky-dory to me. The instance declaration brings `a` into scope, and so I shouldn't expect to bring it into scope again in the instance sig. However, I'm...
I agree with @mitchellwrosen that it is odd that `instance Foo a where ...` brings `a` into scope without an explicit forall. But that's orthogonal to this proposal. Thanks, @mitchellwrosen...
But `Base.string` is an abbreviation for `string`. Is that not what `-short-paths` is trying to address?
Ah -- I didn't realize that. I edited the file to be ``` open Core module Foo = Base.Int let _ = Filename.dirname ``` which would seem to force loading...