Ilya Sher

The common pattern of having `main` methods of the form F main(op:Str, ...) { guard op == "myop" # for example "create", "list", "delete", etc } would be better expressed...

jc integration - suggest to install

2

NGS should recommend to install `jc` when NGS is unable parse the output of a command or a contents of a file. ## Parsing a command ``` data = ``some_command``...

... probably Alternatively, the Str should have meta() with the hints

## Requirements * Architecture-independent * (probably) For inter-op with UI clients which run in the browser, one of the formats should be JSON based ## Resources * https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/basic-serialization.md * https://www.baeldung.com/java-serialization

`1 -> X+2` is parsed as `(1 -> X) + 2` instead of `1 -> (X+2)` ``` $ ngs -pi '1 -> X+2' [ERROR 2021-12-13 00:04:43 IST] +----------------------------------------------------------------------+ [ERROR 2021-12-13...

FFI

1

FFI is in early stage of implementation. Needs a bit more thinking and then completing the implementation. https://github.com/ngs-lang/ngs/wiki/FFI-Design

read/write from/to file should be done using some kind of stream object

1

.... and not using the `.fd` field of `File` object.

Currently: ``` $ ngs -pi 'Path("/")' $ ngs -pi 'Path("/", true)' ``` It would be nice to have some more straightforward/obvious way than the second parameter.