Ilya Sher
Ilya Sher
It's actually much worse than not implemented. Background: using the provided docker images (`sparkfhir/spark:r4-latest`) ``` { "resourceType": "CapabilityStatement", "version": "1.5", "name": "Spark", "experimental": true, "date": "2021-01-20", "publisher": "Kufu", "description": "This...
> your naming conventions The whole world's naming convention. This naming is plainly a bug. Nobody calls it that way. > you can fork the repo and change its name...
I'll summarize my position. * This is a bug * Denying that this is a bug - not OK * Saying that I suggest "name that complies to your naming...
Possible design: ``` ns { F build() ... F some_other_target() ... } ``` * Run with `./myfile.ngs::build` or `./myfile.ngs::some_other_target`. * Default file would be `ngsfile`, run with `ngs ::build`, `ngs...
Next design: `ns`, like in previous design. If `main()` does not exist or does not match the arguments, the method is looked up in the namespace and the called with...
Thought: `v.assert(Int) =~ pattern`
This will be much more useful when globbing (`ls *.txt xyz* etc`) is supported.
must include vim highlighting
The package should include vim highlighting
Any of them will work. Apparently you need to be organization member to be assigned to a ticket. I've just sent invitation.