[Files\write] function segfaults when writting a `:dictionary` without .json option

[RickBarretto]

Summary

Function segfaults when passing a :dictionary. In this case, I'm not passing .json attribute to it.

Current Behavior

$> example: #[target: "/home" search: "Arturo"]
$> example >> "example"
SIGSEGV: Illegal storage access. (Attempt to read from nil?)

Expected Behavior

Should express this dictionary into the file:

$> example: #[target: "/home" search: "Arturo"]
$> example >> "example.art"
$> read ./"example.art"
=> #[
    target: "/home"
    search: "Arturo"
]

Steps To Reproduce

No response

OS

Windows 11

Version

arturo 0.10.0 Arizona Bark (amd64/windows)

Anything else?

For reference, when I use write.json:

$> example: #[target: "/home" search: "Arturo"]
$> example >>.json "example.json"
$> read ./"example.json"
=> {
    "target": "/home",
    "search": "Arturo"
}

Issue reported from official Arturo's VS Code extension.

• VS Code: Visual Studio Code 1.109.3 / Extension: v0.9.1

Is there an existing issue for this?

• I have searched the existing issues

[drkameleon]

That's actually quite interesting. It looks like a bug, but actually it's a new feature.
And one that I would be totally pro-adding: when writing a non-String Arturo value to a file, we'll convert it to code first 😉