amber-lang/amber

Summary Amber is licensed under LGPL-3.0, and the compiled Bash output inlines Amber's standard library functions directly. This makes every generated script a Combined Work under the LGPL, so anyone distributing an Amber-compiled script inherits the LGPL's notice and source-availability obligations. Why it happens The stdlib is not referenced at runtime, it is copied into the output at compile time. These are derivative works of Amber's LGPL stdlib. To distribute the output in compliance, the distributor must: (LGPL §4, Combined Works) §4(a) - give prominent notice that Amber's library is used and is LGPL-covered §4(b) - accompany the work with copies of the GPL and LGPL texts §4(d)(0) - make the corresponding source available (the Amber stdlib version used, plus the application sources) so a recipient can rebuild with a modified library The current generated header carries no license notice at all: #!/usr/bin/env bash # Written in [Amber](https://amber-lang.com/) # version: 0.6

Description Amber does not directly support short-circuit evaluation when functions are used inside inline logical expressions (and / or). Because Amber pre-calculates function outputs into temporary variables before evaluating, all functions in the expression are executed unconditionally. Since Amber compiles to Bash (which natively supports short-circuiting), this behavior is highly counter-intuitive and can introduce side effects or unexpected performance bottlenecks. However, short-circuiting can still be achieved indirectly by using nested statements (eg.: If statements). This architectural difference and its indirect solution should be explicitly documented under the Expressions :: Logical Operations section to guide developers toward idiomatically correct code. Reproducible example no-short-circuit.ab #!/usr/bin/env amber import { date_format_posix, date_now } from "std/date" import { echo_info, echo_warning } from "std/env" fun first_condition(): Bool { echo_info("Startin

To track new stuff for the stdlib. Web server, maybe using python, php and other based on what is found on the machine without implementing a pure bash server (for now) upload way using curl or other solution

What we can do is evaluating a CI for this task in clippy. Ref: rust-lang/rust-clippy#3793 In this way we can have reports about what Rust code can be simplified and we can have newcomers easy task.

Like we did for sudo so the code will be still executed also if the shell is closed. Proposed syntax: let job = async foo() // This calls `bg` detach foo() // This calls `nohup` await job // This calls `fg`