Feature Request: Binary String Literals

[YizhePKU]

Feature Request: Binary String Literals

[fdncred]

I'm moving this to nushell since it's not really about our documentation.

[fdncred]

You mean like 0x[deadbeef]? We also support 0b[101010] and 0o[1234]

[YizhePKU]

@fdncred OK, I think my choice of example is confusing. I mean something like b"Hello world" should be parsed as a 11-bytes binary blob.

This is different from 0x[deadbeef], which is a 4-bytes binary blob.

[fdncred]

in your "patching" example, bytes replace wants to use 0x[123] format for matching/replacing bytes.

you can also do "hello world" | into binary to get the binary data.

[YizhePKU]

you can also do "hello world" | into binary to get the binary data.

Exactly. I'm just suggesting a syntax shortcut for this. Without this syntax, I'll have to write:

open ./a.out | bytes replace --all ('deadbeef' | into binary) ('livebeef' | into binary)

This is the same syntax used by Python and Rust to specify bytes literals.

[YizhePKU]

By the way, does into binary make any guarantee about text encoding? I don't see this mentioned in the docs.

[fdncred]

I'm not sure. You'd have to look at the code. https://github.com/nushell/nushell/blob/main/crates/nu-command/src/conversions/into/binary.rs