Jeremiah Senkpiel

I'm not 100% sure what implications this would have for Node.js, I don't think Heap Snapshots are currently programatically available or where we would put them, but It could be...

Would it be an option to not spec it and recommend moving those users to a better API? Could we get some ecosystem usage stats?

Possibly. Does anyone think printing JSON as a formatter is useful?

I don't suggest following us unless we decide it is useful / a good idea. --- These are the relative code bits for `%j` in Node.js: https://github.com/nodejs/node/blob/7b924f1713006219e20ae7f011405d18b3ac7426/lib/util.js#L95-L102 & https://github.com/nodejs/node/blob/7b924f1713006219e20ae7f011405d18b3ac7426/lib/util.js#L60-L66 Which...

> An important thing to consider in standardization discussions is the concept of the shortest path to interop. If Node simply removes %j, we have achieved interop. Removing features from...

> Why not just alias %j to %O and spec out non-interactive object? two birds one stone I think it's more of a question if anyone finds the JSON output...

My impression when we last considered it for Node.js was that it was the user's responsibility to clean it up. I'm unsure how much stack/tick tracing we would be willing...

You should already be able to import enum variants directly: ```rust use CompassPoint::West ```

Ah I think I understand better now - the `_` would be scoped to the type in the `match`. I agree this (or something like it) would be _very_ nice!

Sorry to be another person on this, but I have a lot of free time right now and also past RFC experience... @GoldsteinE are you still working on this or...