rtfeldman

9 ms·

61.
by rtfeldman 2y ago
As the FAQ entry notes, one of the "sides" in the design space here is "a fragmented ecosystem is best because there's no other way to accommodate the variety of different styles people want to use" - this is a tota
62.
by rtfeldman 2y ago
In Haskell terms, Roc's `Task ok err` is essentially an `IO (Either err ok)` - the only difference between how Roc does it and how Haskell does it is that `Task` bakes in error handling whereas `IO` doesn't. (Plus the syntax sugar
63.
by rtfeldman 2y ago
Roc actually doesn't use algebraic effects under the hood, although errors can naturally accumulate in a way that makes the code look more like error handling in algebraic effects systems: https://www.roc-lang.org/tutor
64.
by rtfeldman 2y ago
That's correct - if you wanted to actually run all of them, you could use Task.seq (to run them sequentially, as opposed to concurrently) like so: Task.seq \f -> File.read! f https://www.roc-lang.org/package
65.
by rtfeldman 2y ago
I'm not sure whether you've seen this, but we have settled on a specific design for sharing effectful code across platforms! https://docs.google.com/document/d/110MwQi7Dpo1Y69ECFXyyvDWz... As you noted,
66.
by rtfeldman 2y ago
TIL that Idris also has a very similar `!` operator (in the prefix position instead of suffix) - thank you for sharing!
67.
by rtfeldman 2y ago
Author here - I actually gave a talk about effect systems and Roc awhile back: https://youtu.be/7SidSvJcPd0?si=iwyguLUWIX3FDq9f I thought this particular post already introduced enough terminology without opening up that pa
68.
by rtfeldman 3y ago
Absolutely! More details: https://github.com/roc-lang/roc/blob/ad5ed57c4202f847cf9e215...
69.
by rtfeldman 3y ago
Thanks for the kind words, and thanks for the feedback! > Is there an explicit type hole mechanism as well, for getting the compiler to spit out the types it expects? Not currently, although you can write `_` for any part of a type annot
70.
by rtfeldman 3y ago
Oh I totally agree that it's a good idea to annotate top-level functions even if you don't have to, and better compiler error messages is one of the benefits of doing that. Personally I basically always choose to annotate them exc
71.
by rtfeldman 3y ago
A common example of a tooling problem I've run into with Rust macros is that if I use a string interpolation macro (e.g. in an argument to println!, format!, or dbg!) a lot of VS Code tooling that works outside of macros stops working.
72.
by rtfeldman 3y ago
Glad you've been enjoying Software Unscripted, thank you for the kind words! > 1. Whether they'll support macros, The plan is not to support macros. A major reason is that macros tend to conflict with editor tooling, and I defi
73.
by rtfeldman 3y ago
Oops, that's a bug - just opened an issue for it: https://github.com/roc-lang/roc/issues/6027 Thanks for pointing it out!
74.
by rtfeldman 3y ago
Wow, this is depressing to read. :( 5 years ago I was upset and posted a comment that was unfairly harsh to another commenter. I apologized at the time, and I meant it. I definitely should not have made the harsh comment that I did. It was
75.
by rtfeldman 4y ago
Nice, I didn't realize Forth used them - thank you!
76.
by rtfeldman 4y ago
I'd love to see some implementations of fixed point trig functions, but I haven't found any! Do you have any links by any chance?
77.
by rtfeldman 4y ago
I was upset and said things I regret and which the poster didn't deserve. I apologized but I still feel bad about it. Not that it excuses my behavior, but I have mentioned this elsewhere - e.g. https://old.reddit.com/r&
78.
by rtfeldman 4y ago
I host Software Unscripted - weekly hour-long episodes with a variety of guests: http://software-unscripted.com
79.
by rtfeldman 4y ago
After on-disk caching, the biggest performance improvements I've seen to compilers have been from changing how data structures are allocated/deallocated and laid out in memory. I haven't seen much opportunity to improve algor
80.
by rtfeldman 4y ago
> I honestly fail to see why would a lower level language be faster, especially that compilers are notorious for their non-standard allocation and life cycle patterns, so a GC might actually be faster here. The nonstandard allocation and
81.
by rtfeldman 4y ago
As far as I can tell, the main reason we all spend so much time waiting for compilers is that compilers aren't considered as performance-critical as they should be. My full-time job is making a compiler for a high-level language, and I
82.
Monad Trait in Rust(twitter.com)
1 points by rtfeldman 4y ago|0 comments
83.
by rtfeldman 4y ago
> And since there are all kinds of pointers in D, one no longer can use a moving GC allocator, because it cannot know exactly where 100% of the GC pointers are. I was astonished to learn that researchers found a way to implement a compac
84.
Developers, Please Nurture Your Coding Experience(aymericbeaumet.com)
1 points by rtfeldman 4y ago|0 comments
85.
by rtfeldman 4y ago
There was a great talk at Strange Loop about a drop-in malloc replacement which compacts. Apparently it actually led to memory usage improvements in industrial projects like Redis: https://youtu.be/c1UBJbfR-H0
86.
by rtfeldman 4y ago
NoRedInk | Full-Stack Engineers, Senior Full-Stack Engineers, Principal Full-Stack Engineers, Frontend Accessibility Engineers, Growth Engineers, Quality Assurance Engineers, and Engineering Managers | REMOTE from time zones between (and in
87.
by rtfeldman 4y ago
> I firmly agree with Rust's choice not to implement the SSO optimisation in the standard library's String type. Out of curiosity, why is that? I don't know much about how or why that decision was made, but I'm curiou
88.
by rtfeldman 4y ago
NoRedInk | Full-Stack Engineers, Senior Full-Stack Engineers, Principal Full-Stack Engineers, Frontend Accessibility Engineers, Growth Engineers, Quality Assurance Engineers, and Engineering Managers | REMOTE from time zones between (and in
89.
by rtfeldman 4y ago
NoRedInk | Full-Stack Engineers, Senior Full-Stack Engineers, Principal Full-Stack Engineers, Frontend Accessibility Engineers, Growth Engineers, Quality Assurance Engineers, and Engineering Managers | REMOTE from time zones between (and in
90.
by rtfeldman 5y ago
NoRedInk | Full-Stack Engineers, Senior Full-Stack Engineers, Principal Full-Stack Engineers, Growth Engineers, and Engineering Managers | REMOTE from time zones between (and including) Pacific Time (PST) through Central European Time (CET)

More ›