Louis Gesbert
> Sounds nice! However, there is currently only Java, Scala, Typescript, Python and OCaml supported by ATD right now. This means that to add backends you'll have to contribute to...
NOTE: #671 has a (pretty dumb) implementation of equality tests instanciation in [lcalc/expand_op.ml], useful for the C backend as a placeholder. But it'll need to be replaced by something better,...
Thanks @lsylvestre !
Yes! Maybe `foo at state one` ? Important note: this should be available only within the scope where the variable is defined.
Hm I have an additional interrogation here: - Accessing `foo state one` from another definition within the same scope → ✅ - Accessing `foo state one` from another scope →...
Can indeed reproduce, thanks for reporting. At the moment we are bound to a tweaked (and fixed) version of the Ace editor, which comes with many bugs and weirdnesses (in...
That looks pretty good to me! For the targets maybe something more atomic would be more convenient: repeating a `[[target]]` section for each of C, OCaml, LaTeX, HTML. For either...
That's not expected to happen; the mechanism opam uses to revert its previous changes is to lookup the `OPAM_SWITCH_PREFIX` variable, read the file `.opam-switch/environment` below it, and "undo" that (on...
This is indeed a limitation of Ninja: the "key" identifying a target is a specific PATH, without resolution of the underlying file of any kind. I admit it's a sane...
Not really sure where this would be useful: it would basically allow to write to `/usr/etc` (or `~/.opam/some-switch/etc`, even) rather than `/etc` ?