Daniele Scasciafratte
Daniele Scasciafratte
So checking my experimental script to evaluate improvements to Amber https://github.com/Mte90/My-Scripts/blob/master/dev/lsp-installer/install.sh We can see as today tons of `__AS=$?` that are useless.
So https://github.com/amber-lang/amber/blob/master/src/modules/condition/failed.rs#L95 adds the useless variable. I think that this code should check if the next line in the amber code is checking for the `status` variable.
Maybe the approach should be the apposite looking at the code. We add `__AS=$?` basically at every command, instead when it is called `status` we should add it the line...
Seems the best way, maybe with https://docs.rs/comment-parser/latest/comment_parser/ we can implement easily?
So we want follow the jsdoc standard or one c style?
If we will go on `/** */` syntax we can approve? https://github.com/Ph0enixKM/Amber/pull/238 So in the way I will add all the comments in the stdlib
I think that also comments can include parameters. I think that can be interesting define script parameters like wp-cli does in a comment: https://github.com/wp-cli/wp-cli/blob/main/php/commands/src/Help_Command.php#L9 In this way the help is...
We have now documentation with `\\\` and is not added in the bash file but with 2 ues
Something like ``` sudo { apt install etc } ```
I think that Amber in that case will add on the first `sudo` usage (whatever the implementation is), block the execution if `sudo` is not available on top of the...