probably gets better with use but having to remember not to put a loop as the last statement of a function, because it would make it return an array of the last statement of the loop body, caught me off guard enough times to get annoying.
easy enough to add an extra line with just 'undefined' as the last statement of the function of course. but then you do need to remember that.
You can definitely use ReleaseSafe, you can also switch modes during compilation. so you can call '@setRuntimeSafety(false)' at the start of a scope to disable runtime safety for performance critical sections.
while we're wishing for impossible things i'd also love if the consent dialogs were an actual standard. if sites could describe a list of what they needed consent for and the browser supplied the actual dialog, so i could just configure it to always allow all if i wanted to, that would be fantastic.
You can get a good quality SLA printer for $200-300, and you can buy FDM printers for tens of thousands of dollars. Just depends on what audience they're targeting.
From what I've seen that's kind of overselling it, his own family hasn't claimed that he said that, an anonymous person who claimed to be a friend of his did.
But I may have missed any further developments to actually verify that his family had been told something similar.
Back around 2002 at least there were some products, ABCpdf is one I used a lot, which ran Internet Explorer on the server to generate PDFs from HTML. Worked pretty well from what I recall.
the phone is likely linked to an apple account. seems reasonable that if the components are approved for a specific phone and that phone is linked to an icloud account, that account could permit a swap?
For me, Rusts SQLx has been a good option for this. Write plain SQL with a macro and have it verified against a dev database at build time, optionally to a typed anonymous struct to match your query results. The performance isn't incredible though.
Personally I've never had an issue reading through the source for zig std, and if your editor supports it you can just 'go to implementation' on most things. Hopefully the code remains relatively readable since I find it preferable to see the actual code + some basic tests rather than trying to navigate those documentation sites.
It's true the NES has 2 KiB built-in RAM, but a cartridge can provide its own RAM. Some of the later cartridges (MMC5 for example) supported up to 128 KiB of extended RAM. There's not really any limit to how far you could push that with a custom mapper.
Not so sure about any real IDEs, lldb has worked fine for the (fairly small) zig programs I've worked on and the "CodeLLDB" vscode extension worked. Of course with the move from LLVM i assume lldb will stop working, and vscode may not be a good enough debugging experience.
I would say in something like speedrunning there is tons of information that only exists in discord pinned threads etc., and in the combined heads of community members.
To those who care about that hobby a lot of very useful information would vanish if discord went away. That's not a great state of affairs and discord is a very bad place to keep that information, even at the best of times it's not easy to find things in there. But I think it's probably the case for a decent number of communities.
You could definitely argue that it's not historically relevant, since, if speedrunning as a whole disappeared it wouldn't really matter.
easy enough to add an extra line with just 'undefined' as the last statement of the function of course. but then you do need to remember that.