Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
leshow
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
50 ms
·
511.
▲
by
leshow
8y ago
A Set would be even better IMO
512.
▲
by
leshow
8y ago
Why don't you just use a set?
513.
▲
by
leshow
8y ago
> feasible: possible to do easily or conveniently. > likely; probable. Support for monads in Rust is not possible to be added easily to the language, nor is it particularly probable. The features that come with the imagined syntax in
514.
▲
by
leshow
8y ago
That's what scares me
515.
▲
by
leshow
8y ago
Is this something just chrome is implementing or is this actually part of the HTML standard now?
516.
▲
by
leshow
8y ago
There's no discussion of implementation, we have no idea how "reasonable" an implementation would or wouldn't be. My assumption from reading this is it would require a ton of non trivial additions to the type system
517.
▲
by
leshow
8y ago
I'm not sure what parts of FP python has you're referring to but it seems pretty lacking. It has a few combinators, that's about it. The influence of "FP" on rust is really more like the influence of Haskell's
518.
▲
by
leshow
8y ago
Pretty misleading to write "... I want to demonstrate that monads are feasible in Rust." if that's not actually the case
519.
▲
by
leshow
8y ago
> Except if the main point is "monads are feasible in rust if we add these features". This is just showing imaginary syntax though, it doesn't speak at all to whether implementing these features is actually possible. Just
520.
▲
by
leshow
8y ago
Does any of this actually compile? Even with generalised_associated_types enabled I couldn't get the Functor definition to compile with a `trait MapFn...` edit: If the main point of the article is to show that 'monads are feasible
521.
▲
by
leshow
8y ago
There are a million and a half monad blogs out there. I, for one, am happy not to have to read another "a monad is..." blog post.
522.
▲
by
leshow
8y ago
I'm not surprised that the official Go survey showed: "..Go is the top language they'd prefer to use..." It doesn't really say much given the selection bias.
523.
▲
by
leshow
8y ago
should read: "It's not wrong to describe these operations as monoidal..."
524.
▲
by
leshow
8y ago
Have a look at this blog post, it contains the bit I got that fold description from: https://philipnilsson.github.io/Badness10k/algebraic-pattern... Back to my first post, I don't think it's not wrong to desc
525.
▲
by
leshow
8y ago
There is a requirement for identity, take sorting for example, you need to be able to sort the empty set. It's a monoidal operation. The same is true for folds: fold(xs) = fold(xs ++ []) = fold(xs) ++ fold([]) fold(xs) = fold
526.
▲
by
leshow
8y ago
> I don’t know whether this particular thing really has anything to do with programming, I just remembered I thought it was cool. There's so many cool things related to programming & monoids. For example, monoids are parallelize
527.
▲
by
leshow
8y ago
This is giving me an error: > rustup component add miri --toolchain=nightly info: downloading component 'miri' info: installing component 'miri' info: rolling back changes error: component manife
528.
▲
by
leshow
8y ago
Given the vanilla error handling is my favorite of the lot, I don't really consider it a bad thing that people are moving away from it. There are some downsides, like the lack of stack traces, but it's a nice pattern. Does it have
529.
▲
by
leshow
8y ago
I have a feeling people will read this blog post and implement it by stating some of those observations are going to come across really passive aggressive.
530.
▲
by
leshow
8y ago
Things that have changed: - NLL (non lexical lifetimes) are now in stable, so working with lifetimes and references is a bit easier - stack traces: failure is still around, it's got a fairly large group using it, it seems. I prefer the
531.
▲
by
leshow
8y ago
Personally, I like Rust's a bit better: https://github.com/TeXitoi/structopt edit: because it's type safe!
532.
▲
by
leshow
8y ago
I used awesome for a few years and while I think you're correct to say it does try to do both, in reality it ends up doing neither very well, IMO.
533.
▲
by
leshow
8y ago
I think the key difference here is the use of multiple virtual desktops in the tiling case. In my setup I typically have one vdesk for browsing, one for docs, one split between code/terminal. I may have others open for chat and music,
534.
▲
by
leshow
8y ago
Playing devil's advocate, many firefox extensions don't work as well or at all as they used to. tree style tabs can't integrate in the same way without extra modification, all of the FF extensions that allowed you to control
535.
▲
by
leshow
8y ago
pepperflash plugin, the flash runtime that chrome includes, is about 20mb.
536.
▲
by
leshow
8y ago
> You could of course argue that by preventing the user from doing certain things you avoid some classes of errors. However, I will in turn argue that by forcing the user to write code for the benefit of the type checker often results in
537.
▲
by
leshow
8y ago
STM in Haskell is really nice to use also.
538.
▲
by
leshow
8y ago
from the article: > Notice that this article does not include Go, a language that admittedly has an elegant concurrency solution as well (Go channels) because that solution is not actually thread-safe - it's not very hard to have
539.
▲
by
leshow
8y ago
Link?
540.
▲
by
leshow
8y ago
I've always found Go's 'guiding principles' to be highly subjective, the annoying thing about it is that they are masqueraded as objectivity. Simplicity and readability for whom? If you've been writing C and Java fo
More ›