Carl Mäsak
Carl Mäsak
The `INSTALL` file talks about a `./bin` directory, but there's only a `./scripts` directory in the source tree. Similarly, the `README` file talks about `./lib`, but there's only `./src`.
``` "C is a callable object that takes a C to convert and a C that specifies the direction of the conversion: to UTC if true, from UTC if false."...
Issue #302, that enormous discussion that hovers around fexprs and Kernel but sometimes veers out into the unknown and asks really deep and important questions about computation itself (and how...
Courtesy of @arnsholt. Slightly made-up but complete example: my employee = { name: "Frank", age: 44, role: "Senior Janitor", printName() { say(employee.name); }, printAge() { say(employee.age); }, printRole() { say(employee.role);...
Re-reading [this old comment](https://github.com/masak/alma/issues/294#issuecomment-392330477) made something click for me. In short, access paths need to be a protocol. I don't think "protocol" has ever been defined clearly in the Alma...
So, I was thinking about this. I almost feel ready to open a PR about it. We're in a nice place with this one, because we already have several "waiting...
Assuming a `.has` method on all containers that can do indexing, a `prefix:` macro would make it possible to write if exists container["foo"] { ... } rather than if container.has("foo")...
Why modules and module imports? Because eventually we'll want to play around with macros that affect the parsing context that imported them. I have no reasonable basis for choosing either...
Whenever I need to go in and debug some scoping/lookup bug (as I am currently), I find myself injecting `say` statements in always the same places. Here's what I would...
Just like a module file can have a `MAIN` function, it can also have one or more functions marked with an `is test` trait (or #257 a `@test` annotation). Presumably,...