Re:Catching use-after-move C++ bugs with Clang's consumed an...
by arcticbull on Wednesday July 10, 2019 @05:46PM
(#20406943)
I'd love to hear your thoughts on Rust having an in-house type system and functional programming paradigm. It doesn't seem all that different than comparable era languages like Swift (maybe through inspiration) or Haskell. Macros, are IMO, where things go a little wonky but once you learn you can actually trust the compiler it's easy to let go.
[ Parent
| on HN ]
Re:Catching use-after-move C++ bugs with Clang's consumed an...
by Animats on Wednesday July 10, 2019 @09:23PM
(#20408305)
That's it exactly. If you're into Haskell or Swift, Rust isn't that strange. To a C or C++ or Go programmer, Rust is very strange.
Rust has some brilliant ideas, but it's too hard. Go is rather dumb, but good for getting server-side applications running.
Re:Catching use-after-move C++ bugs with Clang's consumed an...
by blub on Saturday July 13, 2019 @03:04PM
(#20429599)
Surprised to see that you put Swift in the same bucket as Haskell, since Swift is to me the prime example of successfully balancing power with usability in language design.
This is where languages like Haskell, Rust and others fail: the programming language nerds take over and design a language for themselves, making it weirder and weirder as time passes and new arcane features are added.