nushell/.cargo/config.toml

[target.x86_64-pc-windows-msvc]
# increase the default windows stack size
# statically link the CRT so users don't have to install it
rustflags = ["-C", "link-args=-stack:2147483648", "-C", "target-feature=+crt-static"]

# keeping this but commentting out in case we need them in the future

# set a 2 gb stack size (0x80000000 = 2147483648 bytes = 2 GB)
# [target.x86_64-unknown-linux-gnu]
# rustflags = ["-C", "link-args=-Wl,-z stack-size=0x80000000"]

# set a 2 gb stack size (0x80000000 = 2147483648 bytes = 2 GB)
# [target.x86_64-apple-darwin]
# rustflags = ["-C", "link-args=-Wl,-stack_size,0x80000000"]

# How to use mold in linux and mac

# [target.x86_64-unknown-linux-gnu]
# linker = "clang"
# rustflags = ["-C", "link-arg=-fuse-ld=/usr/local/bin/mold"]

# [target.x86_64-apple-darwin]
# linker = "clang"
# rustflags = ["-C", "link-arg=-fuse-ld=mold"]

# [target.aarch64-apple-darwin]
# linker = "clang"
# rustflags = ["-C", "link-arg=-fuse-ld=mold"]
added .cargo/config.toml to build with bigger stack on windows (#2594) * added .cargo/config.toml to build with bigger stack on windows * updated comments 2020-09-24 05:55:33 +02:00			`[target.x86_64-pc-windows-msvc]`
Statically link the CRT on Windows (#5717) 2022-06-06 02:01:01 +02:00			`# increase the default windows stack size`
			`# statically link the CRT so users don't have to install it`
Limited mutable variables (#7089) This adds support for (limited) mutable variables. Mutable variables are created with mut much the same way immutable variables are made with let. Mutable variables allow mutation via the assignment operator (=). ❯ mut x = 100 ❯ $x = 200 ❯ print $x 200 Mutable variables are limited in that they're only tended to be used in the local code block. Trying to capture a local variable will result in an error: ❯ mut x = 123; {\|\| $x } Error: nu::parser::expected_keyword (link) × Capture of mutable variable. The intent of this limitation is to reduce some of the issues with mutable variables in general: namely they make code that's harder to reason about. By reducing the scope that a mutable variable can be used it, we can help create local reasoning about them. Mutation can occur with fields as well, as in this case: ❯ mut y = {abc: 123} ❯ $y.abc = 456 ❯ $y On a historical note: mutable variables are something that we resisted for quite a long time, leaning as much as we could on the functional style of pipelines and dataflow. That said, we've watched folks struggle to work with reduce as an approximation for patterns that would be trivial to express with local mutation. With that in mind, we're leaning towards the happy path. 2022-11-11 07:51:08 +01:00			`rustflags = ["-C", "link-args=-stack:2147483648", "-C", "target-feature=+crt-static"]`
update comments, add other targets (#4891) keep these other targets in case we need them in the future 2022-03-22 14:27:48 +01:00
			`# keeping this but commentting out in case we need them in the future`

			`# set a 2 gb stack size (0x80000000 = 2147483648 bytes = 2 GB)`
			`# [target.x86_64-unknown-linux-gnu]`
			`# rustflags = ["-C", "link-args=-Wl,-z stack-size=0x80000000"]`

			`# set a 2 gb stack size (0x80000000 = 2147483648 bytes = 2 GB)`
			`# [target.x86_64-apple-darwin]`
			`# rustflags = ["-C", "link-args=-Wl,-stack_size,0x80000000"]`
add commented out mold linker usage (#7081) 2022-11-10 15:41:06 +01:00
			`# How to use mold in linux and mac`

			`# [target.x86_64-unknown-linux-gnu]`
			`# linker = "clang"`
			`# rustflags = ["-C", "link-arg=-fuse-ld=/usr/local/bin/mold"]`

			`# [target.x86_64-apple-darwin]`
			`# linker = "clang"`
			`# rustflags = ["-C", "link-arg=-fuse-ld=mold"]`

			`# [target.aarch64-apple-darwin]`
			`# linker = "clang"`
			`# rustflags = ["-C", "link-arg=-fuse-ld=mold"]`