That’s not a segfault, that’s a bus error, which also refers to memory, but it’s a different kind of error, typically occurring when you access a misaligned address or some address which cannot possibly be referenced. Probably a problem with one of the pre-built binaries some npm module ships
fresh new project so no git history .i just copy pasted few configuration files (from my personal boilerplate.) and install all the node modules.i’m guessing some package was missing or something.
This looks like how React components are written if you make the weird choice of not using the JSX syntax extension for React elements. I wonder if you could make a JSX-like DSL with Rust macros. JSX really helps for making this kind of stuff bearable.
Or a better idea: don’t use goto. In any language. Especially not one that needs line numbers to work and not labels, as soon as someone edits the file utter chaos will ensue. This has all the normal downsides of gotos with labels, but with far more downsides.
If you have a format string that long with arbatary expressions putting them all raw in the format string is not going to improve much. Better to give them actual names first.
which is more useful than variables would be. I guess i could use .join or a crate like concat_string? Either way i sorely miss arbitrary expression format strings from python =(
As far as I remember, the point for not allowing arbitrary expressions is that it makes what looks like formatting an arbitrary complex operation and that it doesn’t improve readability that much.
Although sometimes I miss being able to refer to fields in format, for function calls and especially this many, I agree with an advice to put strings in a vector and joining them. Plus, there is a limit to how many arguments format macro can accept, iirc
it makes what looks like formatting an arbitrary complex operation and that it doesn’t improve readability that much.
What’s silly to me about that reasoning is that all workarounds are equally less convenient, have less readability, and the effect is identical to just letting me put whatever between the brackets. I genuinely dont understand the downside i guess.
Calling .join on a vector can have side effects too, except the “we’re concatting strings” is at the end rather than the beginning (and could obfuscate the fact that the end result is a string). It has just as much room for abuse as a long format!(). Even with just format!(), anything you could do inbetween the brackets, you can do outside the brackets in the arguments anyway. At least when it’s between the brackets, i know exactly where it’s going and when without having to juggle the string pieces and assemble them in my head.
Well, that’s all true from an end user perspective. But consider that format! is a macro and as such it should process its format string. Calling something from inside evaluation of a format string really does seem weird in that regard
programming_horror
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.