You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I gave a very preliminary talk on this back in June, but at that point it was more of an idea than something concrete. I've now released a library "haskell_bits" which surprisingly caused some controversy on Reddit and on Twitter.
But despite the suggestion that this "Makes me feel like gouging my eyes out", I'm planning on pursuing it further, even considering the risk of Oedipus style consequences.
Regarding timing, there's no particular rush, as discussed in the current readme there's a number of things still to do, and it's very incomplete and proof of concept at the moment. Having a talk later would allow me to present hopefully a more complete picture, perhaps with some more practical usage examples. But the downside to that approach is that there will probably be more to cover, so smaller talk sooner might also be better. I think they both have their pros and cons so I don't mind either way and happy to fit in with others or whatever people think best.
The text was updated successfully, but these errors were encountered:
clintonmead
changed the title
"Haskell Bits": The Functor/Applicative/Monad hierarchy in Rust
[Proposal] "Haskell Bits": The Functor/Applicative/Monad hierarchy in Rust
Jan 7, 2020
Hi Clinton, we don't have our next meetup planned yet but I think we have enough speakers for that whenever it happens, so probably looking at our 2nd 2020 meetup I'd say. In any case I will let you know.
I gave a very preliminary talk on this back in June, but at that point it was more of an idea than something concrete. I've now released a library "haskell_bits" which surprisingly caused some controversy on Reddit and on Twitter.
But despite the suggestion that this "Makes me feel like gouging my eyes out", I'm planning on pursuing it further, even considering the risk of Oedipus style consequences.
The Readme for haskell_bits gives a rough outline of what I'd like to cover.
Regarding timing, there's no particular rush, as discussed in the current readme there's a number of things still to do, and it's very incomplete and proof of concept at the moment. Having a talk later would allow me to present hopefully a more complete picture, perhaps with some more practical usage examples. But the downside to that approach is that there will probably be more to cover, so smaller talk sooner might also be better. I think they both have their pros and cons so I don't mind either way and happy to fit in with others or whatever people think best.
The text was updated successfully, but these errors were encountered: