Changelog History
Page 1
-
v0.2.8 Changes
🔄 Changed:
- 👀 Implemented work-around for issue 50. See the section in the
README
on known issues.
- 👀 Implemented work-around for issue 50. See the section in the
-
v0.2.7 Changes
September 17, 2017🆕 New:
- Several environment variables are now given to scripts by
cargo-script
.
🔄 Changed:
- Overhauled
README.md
.
🛠 Fixed:
- ⚠ Warning in the new
expr
template.
- Several environment variables are now given to scripts by
-
v0.2.6 Changes
September 13, 2017🛠 Fixed:
- Incompatibility with the version of Cargo shipped with Rust 1.16.0.
-
v0.2.5 Changes
September 07, 2017🆕 New:
➕ Added support for expression script templates.
The built-in templates used for scripts can be overridden.
🛠 Fixed:
- 🏁 Cargo script hanging on build failure on Windows.
-
v0.2.4 Changes
🆕 New:
- Expressions can now use
try!
/?
for propagating errors.
- Expressions can now use
-
v0.2.3 Changes
August 27, 2017🛠 Fixed:
- Suspiciously absent 0.2.2 features.
-
v0.2.2 Changes
August 27, 2017🛠 Fixed:
cargo-script
no longer gets confused when trying to run scripts with non-identifier characters in their name.Coloured output from
cargo
now works on *nix.👍 Relative paths in manifests for dependencies are now supported.
-
v0.2.1 Changes
August 04, 2017🔄 Changed:
cargo-script
now interrogatescargo
to find out where it puts the compiled executables. This should makecargo-script
more robust. This only works with Rust 1.17 or higher.
-
v0.2.0 Changes
July 27, 2017🆕 New:
➕ Added
--test
and--bench
flags. These can be used to run a script's tests and benchmarks.➕ Added
cargo-script file-association
subcommand for managing file associations on Windows.🏗 If compiled with the
suppress-cargo-output
feature,cargo-script
will hide output from Cargo if the build takes less than 2 seconds and succeeds.
🔄 Changed:
🏗
cargo-script
now requires Rust 1.11 to build.✂ Removed prefix manifests. All other forms are still supported.
The cache location on not-Windows when
CARGO_HOME
is defined is now$CARGO_HOME
, rather than$CARGO_HOME/.cargo
. Existing data may be migrated to the new location using the--migrate-data
option.
🛠 Fixed:
The result of an
--expr
invocation now lives longer, allowing borrowed values to be displayed more easily.🛠 Fixed issue with expressions containing commas on the command line.
-
v0.1.5 Changes
🆕 New:
🏗
cargo-script
now (typically) defaults to using a shared build location. This means that, provided you're using the same compiler, dependencies won't need to be constantly re-built. This can be explicitly controlled by setting the--use-shared-binary-cache
option toyes
orno
.➕ Added
--unstable-feature
option. This allows you to specify unstable language features that should be enabled.
🔄 Changed:
- 🏗 The build cache will be retained when the build fails. This means that dependencies don't have to be re-built when the script itself has an error in it.
🛠 Fixed:
- 🛠 Fixed issue with evaluating an expression containing macros that capture.