malcolmstill

5 ms·

1.
by malcolmstill 3y ago
Can you define your use of DP here? I'm not sure if you mean dynamic programming, or design pattern or something else, and am curious about your insight.
2.
by malcolmstill 4y ago
I see you what you mean. Yeah, I suppose if you are writing a library you might want to be more deliberate in the error set. Maybe explicitly writing out the error set is what you want in that situation. Rewriting the example: fn some
3.
by malcolmstill 4y ago
I did use the example of long run of module names, and I do take your point about `use` (though I have to sometimes read the very top of a file too!)...but the same applies to a lesser extent to the "last mile" module (e.g. `Strin
4.
by malcolmstill 4y ago
> Doesn't that risk introducing accidental breaking changes by adding a new error to the set in the implementation, since the set of errors is inferred from the implementation? Do you have an illustrative example? (I'm not impl
5.
by malcolmstill 4y ago
So usually you don't have to specify the error type. The Zig compiler works out what errors are returned from the function by looking at any errors returned directly or errors returned from other functions called within the body of the
6.
by malcolmstill 4y ago
To be honest that's the major one for me. Someone else has mentioned lifetime annotations, but those uncommon enough that I don't find it much of an issue. If I was to think about it: comparing rust to zig, zig benefits a lot from
7.
by malcolmstill 4y ago
There are a number of sources of noise in rust, but the one I find most annoying (because it's also so common) is the double colon. My current theory is that it's because the colon is the same height as lowercase letters. If you e
8.
by malcolmstill 4y ago
> If a test never fails, is it a good test? If I have to change a test everytime I change the implementation, is it a good test? Writing good tests is really difficult. If you don't like writing / maintaining tests or don'
9.
by malcolmstill 4y ago
To expand on the parent and grandparent: Laremere is correct in that there is no "magic" built-in understanding of iterators in the language, i.e. under the hood calling a `.next()` method, without explicitly having to call it. Th
10.
by malcolmstill 4y ago
I could write this against a few other replies but I will write it here. Moreover, I don't think I'm going to say anything that hasn't already been covered by other people, but I am going to attempt to distil down the argume
11.
by malcolmstill 4y ago
The Wayland protocol is fine and provides the modern features expected (“every frame is perfect”). But X is two things: a protocol and a de facto standard server that window managers could easily interface with. I wonder if we’d be in a dif
12.
by malcolmstill 5y ago
> Things that are easy in React at runtime turn out to be surprisingly difficult in Svelte Do you have some specific examples?
13.
by malcolmstill 5y ago
It could be related to historic Scotland -> Poland immigration: https://en.wikipedia.org/wiki/Scottish_diaspora#Poland
14.
by malcolmstill 6y ago
Of all the absolutely fantastic stuff that Zig gets right, I think my favourite is the error handling. While it would be cool to get an error payload, I would hope that if that was added to the language, that it doesn't affect the curr
15.
by malcolmstill 7y ago
Assuming independent events (a bad assumption no doubt) then you're looking for 1 - the probability that for 20 years straight you don't have the event happening. - E event happens in given year - N event doesn't happen in gi
16.
by malcolmstill 8y ago
To clarify, the position is in Newcastle, Edinburgh or Remote within the UK.
17.
by malcolmstill 8y ago
SoPost | Edinburgh, London, Newcastle, UK | REMOTE SoPost is on a mission to build the world's best product sampling platform, and we are hiring into our platform team. We are currently seeking engineers (design, operations and program
18.
by malcolmstill 10y ago
I'm writing a Wayland compositor in Common Lisp: https://github.com/malcolmstill/ulubis