evincarofautumn

33 ms·

1.
by evincarofautumn 6y ago
Wow, I honestly wonder if this was caused by mixing up “functor” in the C++ and Haskell senses… To expand on that, for those in the audience: In Haskell, a functor is a type constructor (like “list”, “optional”, “future”, “I/O request”
2.
by evincarofautumn 6y ago
Cool, thanks! I’m thinking about a similar sort of coercion system for a language project, and it’s good to have a slightly broader view of the design space. This area hasn’t been very well explored yet, not just in terms of semantics, but
3.
by evincarofautumn 6y ago
Has there been any work in Rust on something like Haskell’s ‘Coercible’? Namely, it defines the precise criteria for safe zero-cost coercions between types that provably have the same representation, and derives the coercions automatically.
4.
by evincarofautumn 8y ago
I would love to use it for my compiler backend…if I could find any maintained standalone implementations of it.
5.
by evincarofautumn 8y ago
This is also exactly how male countertenor singers produce a female-sounding voice, by making the vocal cavity smaller to adjust the formants upward. If you don’t do that, it just sounds like a male head voice or falsetto.
6.
by evincarofautumn 8y ago
I have an extremely strong sense of smell, inherited from my mother. Both of us are able to detect smells at lower concentrations and identify them more accurately than almost anyone else I know. My partner has told me that there are many t
7.
by evincarofautumn 8y ago
Of course, the definition we actually use is this: -- (1) fix f = let x = f x in x Because it has better memory usage; the definition you provided is translated to the following STG: -- (2) fix f = let x = fix f in f
8.
by evincarofautumn 8y ago
My working model for why colours admit description more readily than smells is that we judge and decompose them in largely the same way, but it’s simply easier to develop a repertoire of colours. They’re everywhere, most people have decen
9.
by evincarofautumn 8y ago
> It basically combines futuristic tech with dystopian/utopian elements, and grimy, old-world stuff. In other words, “The future is already here—it’s just not very evenly distributed” — William Gibson. And it will probably always be
10.
by evincarofautumn 8y ago
What can we do as individuals? I already eat relatively little in the way of animal products, don’t drive much, don’t use a lot of electricity or natural gas at home…but one person behaving this way isn’t enough. The only way I see us fixin
11.
by evincarofautumn 8y ago
> Does Facebook own your IP? No, afaik it should still be owned by the startup incubator that was the parent company of Spaceport. We open-sourced some ancillary bits and pieces before leaving, but not the most important components of th
12.
by evincarofautumn 8y ago
I worked on a Flash implementation called Spaceport in 2012 or so. We had the most complete implementation apart from Adobe, with all kinds of goodies like actual hardware-accelerated graphics on mobile (far better than the buggy AIR). Trie
13.
by evincarofautumn 8y ago
The language they introduce, Π, is essentially a simple concatenative programming language where all of the primitive combinators happen to be reversible; the graphical depiction is essentially the same as graphical linear algebra¹, which i
14.
by evincarofautumn 8y ago
I don’t mean to evangelise too hard, but this is yet another reason to keep kratom legal in the US. Last I knew, over 30% of the world’s kratom is consumed by the US, and most of that is from Indonesia, specifically Borneo. Kratom is an und
15.
by evincarofautumn 8y ago
I’m not sure, but based on what statistics I can find, it seems most blind people aren’t congenitally blind, so they probably have some familiarity with the symbols, maybe depending on how old they were when their visual impairment manifest
16.
by evincarofautumn 8y ago
Simon Peyton-Jones is (was?) known for writing blocks in “aligned” instead of “hanging” style, with separators in prefix: someFunction = do { foo ; mx <- bar ; y <- case mx of { Just x -> do { baz
17.
by evincarofautumn 8y ago
Right—that was a source of inspiration for this aspect of my language. The original stated motivation in Haskell’s case was to make it easier to generate Haskell source code without needing to worry about indentation, but I wondered if it c
18.
by evincarofautumn 8y ago
The language in question already has a dataflow/pipeline style by default, so expressions are generally read from left to right like this, except for some standard syntactic sugar like infix operators and flow control blocks like “if”
19.
by evincarofautumn 8y ago
Thanks so much for your response! #4 in particular is something I hadn’t considered, except in the context of how to display error messages in an editor, but now it seems obvious that the most relevant information should be closest to your
20.
by evincarofautumn 8y ago
Last I knew, Braille displays are also pretty expensive, slow, and prone to breakage. Cool idea, but doesn’t work as well as a screenreader in practice for most people.
21.
by evincarofautumn 8y ago
My compiler is error-recovering for this reason: you can still get correct syntax-highlighting data even if there are lexical errors, type information even if there are type errors, and so on.
22.
Ask HN: How should a programming language accommodate disabled programmers?
173 points by evincarofautumn 8y ago|116 comments
23.
by evincarofautumn 8y ago
In my accent (a rhotic New England without the cot–caught merger) they’re all different: • “ox” /ɒks/ • “aux” /ɔːks/ • “orcs” /ɔɹks/ But hey, close enough for a pun anyway. My favourite rhymes and puns are th
24.
by evincarofautumn 8y ago
I sometimes dream about being & moving amongst the abstract structures that I build in my head when reasoning about a complex problem. Sometimes it gives me an insight; others, it’s meaningless, the Tetris effect in another form.
25.
by evincarofautumn 8y ago
It’s not so unusual. I learned assembly before I learned C, mostly because I didn’t have a C compiler—or even know that I needed one! My family’s Windows 95 computer had QBASIC preinstalled (which amazingly I learned mostly by browsing the
26.
by evincarofautumn 8y ago
It’s “exactly one byte” in the sense that by definition, sizeof(char) = 1, but it’s “at least one byte” in the sense that CHAR_BIT ≥ 8.
27.
by evincarofautumn 8y ago
A recent Twitter thread about this game, which goes into a little more detail on a couple points: https://twitter.com/Foone/status/1054907948852342784 Something that stuck out to me as cool: > It used a dual-pr
28.
by evincarofautumn 8y ago
I mean if you can’t observe any difference from safe code, then despite having different intensional/operational definitions, they are extensionally equivalent, and that’s mostly what I care about. The ApplicativeDo desugaring, which
29.
by evincarofautumn 8y ago
I think that law is slightly too restrictive; there’s a useful class of Monad instances where it doesn’t hold: commutative monads, in which: x <- f y <- g Is equal to: y <- g x <- f Provided that “x” is
30.
by evincarofautumn 8y ago
Minor point: New York isn’t part of New England. But as for the weather, it’s close enough.

More ›