-
# User Story:
On #538 we are tracking the higher-level issue of developing an idea of "control identity" over and above simply marking a control's `id` flag, for example taking account of catalog o…
-
This one is probably controversial. Emacs 24.3 took setf out of the cl package (at the same time renaming it to cl-lib) and introduced it to the Emacs Lisp core as _generalized variables_ (gv). Many o…
-
# Background
Right now, Elvish always resolves commands at compile time, and it is not allowed to use a dynamically built string as a command. The compile-time resolution only accepts *single strin…
-
-
I find that the syntax for generics is a bit noisy. Is there a technical reason for backticks before type names?
For instance, instead of this:
```lua
local function keys(xs: {`K:`V}):{`K}
```
…
-
Right now the library system isn't really a library system. The compiler just pastes the code for a subset of `rnrs` into every library we compiler. It would be better to be able to load libraries fro…
eholk updated
4 years ago
-
This is related to #13523 and #13524.
If we have a module and a submodule, like this:
``` chapel
module M {
module L {
proc lFunction() { }
}
L.lFunction(); // here
}
```
Shoul…
-
I'm having trouble reviewing what _GetDirectiveContext_ is doing. It seems to make some unstated assumptions about what happens to be on the execution context stack at the time it is called. I can't t…
-
## Actual Behavior
when I have a source code block with the language set to `elisp` or `emacs-lisp` the block will not export properly. Instead it will render like this
```nillangnils…
-
Since this is the [library being used](https://github.com/github/linguist/tree/master/vendor) for [syntax highlighting of fenced code blocks](https://help.github.com/en/github/writing-on-github/creati…