Andrej Kolčin

I checked this right now on the Free Code camp repository and my testing one, and the quoting seems to work properly: ``` Language,Location,Filename,Lines,Code,Comments,Blanks,Complexity,Bytes Python,"dir,with,quotes/another,comma,.py","another,comma,.py",1,1,0,0,0,17 Python,",name,with,commas.py",",name,with,commas.py",1,1,0,0,0,17 ```

I looked into the code and `csv-stream`, unlike the `cvs` format, does not allocate any memory, so it does not use the standard CSV library. There was a bug with...

Work fine on [Ian's range changes](https://github.com/IanManske/nushell/tree/number-range)

This might be caused by some kind of precision issue during deserializing. ```Nushell /tmp> 5e+22 50000000000000000000000 /tmp> "float4 = 5e+22" | from toml ╭────────┬────────────────────────────╮ │ float4 │ 49999999999999995805696.00 │ ╰────────┴────────────────────────────╯...

@fdncred understood. It turns out that tables and the REPL use different display for some reason, and the latter is not affected by `float_precision`. I edited the name to reflect...

@fdncred, I have `float_precision` set to 2, and this is the REPL: ```Nushell ~> [49999999999999995805696.00] ╭───┬────────────────────────────╮ │ 0 │ 49999999999999995805696.00 │ ╰───┴────────────────────────────╯ ~> 49999999999999995805696.00 50000000000000000000000 ```

Ah, no, not yet. Maybe its a part of reedline, since it bypasses the automatic `| table` appending.

TIL there are `seq` subcommands. The issue itself is related to #11721, as this is a panic by `chrono`.

@kubouch I probably made a mistake. I'll dig into it properly this week and either report an upstream bug, or send a PR here.

@kubouch here's the issue, from the `chrono` docs: > This returns a DelayedFormat, which gets converted to a string only when actual formatting happens. You may use the to_string method...