verdagon

35 ms·

331.
by verdagon 5y ago
What would that look like, and why horrible?
332.
by verdagon 5y ago
The author obviously did a lot of research, explained roguelikes' roots, and has an interesting take on something that a lot of the great roguelikes have in common. It was a good read. Also, if you read to the end of the article, they
333.
by verdagon 5y ago
Thanks for sharing these! I see what you mean now. And it's especially unfortunate that Android needs an entirely different OS build. iOS works a bit more like I expected, though they don't list the instructions we might use to sc
334.
by verdagon 5y ago
Was on my phone before, but now I can give a more in-depth reply =) So far, memory tagging is only done per allocation from malloc or alloca. The compiler backend inserts special new instructions (such as STG) to scramble the tag for a spec
335.
by verdagon 5y ago
What I'm saying is, a new language can use memory tagging more effectively, if it decides when to scramble a tag.
336.
by verdagon 5y ago
I can imagine Zig using memory tagging at a more granular level: imagine changing a 16B union's tag when assigning it. C and C++ only do it per-allocation IIRC.
337.
by verdagon 5y ago
I do a lot in the PL space, and Zig has me pretty excited. I think Zig, paired with memory tagging for memory safety, could be a killer combination one day.
338.
by verdagon 5y ago
What are some of the more performant architectures?
339.
by verdagon 5y ago
It's a bit silly to say shared mutable state is morally wrong. Rust programs have shared mutable state in that indices often refer to mutable data, and Java programs allow more conventional shared mutability without memory unsafety. Sh
340.
by verdagon 5y ago
Just so we're clear, you're saying that Rust only takes 15 minutes to learn and be productive in, for the average person?
341.
by verdagon 5y ago
It's a new language named Vale ( https://vale.dev/ ). The TL;DR from a Rust perspective might be "A Rust that embraces shared mutability by default, automatically borrows things, and then adds an opt-in region bor
342.
by verdagon 5y ago
I'm currently designing an "Automatic Rust", something high-level that will automatically implement the usual Rust patterns (generational indices, the occasional Vec or arena, and something I call a LifeCell), so we have fast
343.
by verdagon 5y ago
I've been thinking about how one could get around the Send + Sync requirements, it's a fascinating conundrum, from a language design standpoint. If we didn't have the Send + Sync requirements, and multiple async functions are
344.
by verdagon 5y ago
I believe it has release-safe mode, which protects against most use-after-free. This is sufficient safety for most applications, IMO. I only see it getting safer from here, with some advances on the horizon, such as memory tagging. The lang
345.
by verdagon 5y ago
Wow, that's an impressive collection! Are there any that stood out to you? (I'm especially interested in new memory management techniques)
346.
by verdagon 5y ago
It actually is possible to have decoupled allocation in a memory safe way. We have an open proposal for this in [0], for Vale. TL;DR: Have some bits in the malloc header which instruct the language on which deallocator function to use. I&#x
347.
by verdagon 5y ago
One could say that the point of a borrow checker is to guarantee that you don't deallocate an object until all references to it are gone (for some definitions of deallocate and object).
348.
by verdagon 5y ago
Well said, and I think every new language should take its learning curve seriously. A language should get one of one's way, so they're thinking about their project's inherent complexity, not about the language's complexi
349.
by verdagon 5y ago
Thanks =) I suspect my post was penalized down from the top once I edited in those link citations. HN works in mysterious ways! I've mostly been in the https://reddit.com/r/ProgrammingLanguages subreddit and its d
350.
by verdagon 5y ago
Some more things I see coming soon: * Decoupled allocation, to use any allocator with any existing code. Cone has some really cool things on the way here, where we can package up allocators into modules and others can import them and use th
351.
by verdagon 5y ago
You make a lot of assumptions, and dismiss my valid opinion as uninformed. I would say that's arrogant and offensive, but I'm sure you meant well. More to the point, in my many years of experience with Rust, I've found that i
352.
by verdagon 5y ago
I've discovered a similar pattern, when I look at successful projects in my past. I prioritize "working", then "solid", then "fast" where it's needed. Ironically, it's this principle that makes m
353.
by verdagon 5y ago
I think both are true. Rust is poorly-suited to certain architectures, and empowers us to use other architectures. Rust's idioms take both its strengths and weaknesses into account. It can make up for it in other ways, but in my experi
354.
by verdagon 5y ago
Indeed, ECS might not be a good fit for turn-based games. We explored the topic quite thoroughly in [0] and came to the conclusion that Roguelikes are more suited for something in-between ECS and OO, named just "EC". ECS is better
355.
by verdagon 5y ago
I'd love to hear more, what kinds of incentives? Is it something like, "if you get X efficiency, you get N more dollars"?
356.
by verdagon 5y ago
IIRC, functional programming already offered const-ness and type-safe concurrency. Do you think Rust might succeed here where FP couldn't really make much of an impact?
357.
by verdagon 5y ago
Would you say that Rust's learning curve is also still an obstacle to widespread adoption? It was a while ago, but I haven't asked around lately.
358.
by verdagon 5y ago
The treasuries I've seen are adjusted for inflation, so this won't happen to those. Not sure if there are also un-adjusted treasuries though. Probably?
359.
by verdagon 5y ago
I very much hope Rust becomes popular in the embedded space... but other languages are better for apps IMO. I'd rather use a click listener with TS/Kotlin/Swift than be forced into idiomatic Rust's architectural workarou
360.
by verdagon 5y ago
Type stability lets us mutably alias, which atomics and Cell do not. It doesn't really have a Rust counterpart, a struct containing a bunch of Cells cannot be mutably aliased. If you're curious, this (draft) page has some informat

More ›