leshow

53 ms·

601.
by leshow 8y ago
It probably won't be for you. I was picking up Rust in 2015 and my prior Haskell knowledge (just past beginner at the time), helped immensely. There's a good deal of crossover for the broad concepts.
602.
by leshow 8y ago
Wouldn't be my first recommendation for a good Haskell book. I really enjoyed Haskell: first principles. I'm sure that will get mentioned a lot here. Still, as a free resource it does cover some fun things. I just felt the book wa
603.
by leshow 8y ago
Funny how it was recommended at the start of this thread, in light of that.
604.
by leshow 8y ago
I don't think it's crazy to wish for some kind of interface or trait-like abstraction mechanism in a language. Anything taken to the extreme can sound stupid. edit: I'm not saying Elm should change, the time for that is long
605.
by leshow 8y ago
Your comparison doesn't make any sense. You would use a language like Elm/Purescript/Reason etc for the type safety, that's completely orthogonal to whether something has classes or not.
606.
by leshow 8y ago
The type system is one of the main draws for me.
607.
by leshow 8y ago
The answers here will be subjective, but IMO Rust is useful for a much wider range of things than just 'super low level stuff'. I use it for anything from small command line tools to web backends if I have the option. I appreciate
608.
by leshow 8y ago
> but will still kill you This does not say that 'vaping will still kill you'. It doesn't say anything close. What it says is that in a laboratory over a 48 hour period lung samples exposed to vapour caused inflammation an
609.
by leshow 8y ago
resolution of cognitive dissonance?
610.
by leshow 8y ago
You were just told the formatting removed the asterisk. const isn't a type, but a const pointer is, so is a mut pointer. It says so in the book AND it's in the position of a type in the code. What other information do you need to
611.
by leshow 8y ago
> that's called running apps. And you accuse me of making things up? "Allow third party code" is not called "running apps"
612.
by leshow 8y ago
The application uses google play, which almost every other android application in the world uses by default. And somehow that makes them untrustworthy?
613.
by leshow 8y ago
Build the code yourself
614.
by leshow 8y ago
It seems pretty odd to me to distrust someone because they aren't using the platform that you'd like them to use. Aren't there other issues with f-droid? You have to root your device to run it, allow third party code. Those a
615.
by leshow 8y ago
> This is a strong accusation, I know. The thing which convinced me of its truth is Signal’s centralized design and hostile attitude towards forks. The thing that convinced you that Moxie feels a certain way is that Signal has a '
616.
by leshow 8y ago
It's more than superficial, I struggle to see how using Dart would be at all different from how you would architect an app in Java. It's an OO language with an almost identical set of type system features besides the fact that it
617.
by leshow 8y ago
The asterisk was formatted out. Read the book, they are types.
618.
by leshow 8y ago
> Paraphrasing Qc Na: Subclasses are a poor man's sum type. Also, sum types are a poor man's subclasses. One of the great things about disjointed unions is (usually) exhaustiveness checking. Not to mention usually some form of
619.
by leshow 8y ago
A pointer is absolutely a type in rust. let i: u32 = 1; let p_imm: const u32 = &i; Look at the const u32 in the type position. The rust book even refers to const and mut pointers as types.
620.
by leshow 8y ago
I'm really not a fan of Dart's type system. It feels ancient to me. From what I can tell, there's no sum types, I don't see any way to bound generics based on interface/typeclasses/traits or some other equivale
621.
by leshow 8y ago
Type annotations can be helpful in writing maximally polymorphic code and in self documentation, independent of type inference. When I write Haskell, I still annotate my code.
622.
by leshow 8y ago
The likely reason is B. Elm is a frontend web language that also has this guarantee, and it uses Either types for situations that can fail. It's not entirely unique in that regard, there are other languages (mostly) without exceptions;
623.
by leshow 8y ago
I bought that book 2 years ago, I've since stopped using Elm. It's pretty bad that it still hasn't been released yet.
624.
by leshow 8y ago
Personally, internal mutation is something you should avoid in general. Pretty hard to avoid in OO languages though.
625.
by leshow 8y ago
and pointer chasing too right? unless the runtime can optimize, every generic sits behind a pointer.
626.
by leshow 8y ago
If you've written any amount of Rust then that's provably not true. You've no doubt used functions & methods that use unsafe (somewhere down along the line), and you didn't need to deal with it. That's 'wra
627.
by leshow 8y ago
Could someone write the equivalent of this in Haskell (assuming the GADTs ext). type 'a ty = Int : int ty | Bool : bool ty | String : string ty;;
628.
by leshow 8y ago
If you're looking at rice as a protein source IMO you're looking in the wrong place. It's almost completely a carbohydrate. That's like eating a slice of bread 'for the protein'.
629.
by leshow 8y ago
If it considers parametric types to be interface {}, is that a kind of type erasure? I don't know much about Go, but it's my understanding that interface {} types have an extra layer of indirection and are essentially just pointer
630.
by leshow 8y ago
Can you do ad-hoc or bounded polymorphism? What about recursive types?

More ›