dnautics

8 ms·

151.
by dnautics 3mo ago
exmex is in texas, youre probably thinking of empex
152.
by dnautics 3mo ago
popping inflated egos is the mythology of America
153.
by dnautics 3mo ago
the thing is, as a pattern, footguns in zig are simple and easy to reason about (though they might be hard for an ADHD human to find). the compositional nature of rust sometimes makes footguns "hard to see" because they can be hi
154.
by dnautics 3mo ago
:thumbs up:
155.
by dnautics 3mo ago
classic "can't admit i was wrong" dismissal. nothing special.
156.
by dnautics 3mo ago
yeah rust has no footguns. just dont try to mix clone with iter.
157.
by dnautics 3mo ago
i will not, sorry. but ill probably be at exmex
158.
by dnautics 3mo ago
for about half a year claude code had this obnoxious flicker problem. i almost quit and went to codex over it.
159.
by dnautics 3mo ago
its refinement types which are a "superset of affine types" iiuc (you can construct a refinement type system that can represent affine types, plus more). there is nothing special about zig that makes it fundamentally possible in z
160.
by dnautics 3mo ago
> not suited for real world use. I hope you don't use discord or rely on pagerduty.
161.
by dnautics 3mo ago
i hired a biologist (for my pharma startup) and she produced feature ideas for our internal stack and was guiding claude to write idiomatic code with feedback from my reviews with no coding experience. realistically if you want to start
162.
by dnautics 3mo ago
i ran a quick experiment where instead of doing boxing the way its done in the beam currently, i used a different boxing (NaN strategy and there was a 10x speedup
163.
by dnautics 3mo ago
its been fun building a multiagent personal assistant. (wip, no guarantees, this is the engine i use) https://github.com/ityonemo/ce_ce
164.
by dnautics 3mo ago
> the Zig team would almost certainly build it 1. It's a small team. 2. The zig team is parsimonious about what they do and don't build. For example, they did not work on the language server, rather punting it to the communi
165.
by dnautics 3mo ago
do you want a direct description of the plan for async/alias work? hash the globally accessed gid list and if any operation changes retrigger analysis of all functions in the same execution block with the new layout. i have not had to
166.
by dnautics 3mo ago
> You will not be able to work seamlessly with any regular Zig code. That may or may not be a problem if you're willing to assume you can just use it all unsafely and it works enough that things are fine. that may be true, but it se
167.
by dnautics 3mo ago
did you miss this part? > planned to be addressed i have in mind a strategy to address all of them. this is a side project, a proof of concept, i have other things going on in my life. i dont chip away at it every week. you make, witho
168.
by dnautics 3mo ago
1. it is possible to do code annotations in zig even though i havent implemented it in this iteration of clr (the first poc demonstrated this). i want to see how far i can get without them. 2. let's take double free (easiest to expl
169.
by dnautics 3mo ago
it is possible to do in-code annotations in zig, if you're clever. you can get pretty far without them too. as an example, you can check for double free without ownership tagging, by being agnostic about who should free, and flaggin
170.
by dnautics 3mo ago
start by examining zig-clr
171.
by dnautics 3mo ago
no thats not the definition of more expressive. more expressive means the language can encode more programmer intent without making a dog's breakfast of the code.
172.
by dnautics 3mo ago
1. rust didnt invent affine ownership. 2. It's possible to bolt on to other languages (see ada). zig in particular is easy (disclaimer: i think, i haven't implemented it yet)
173.
by dnautics 3mo ago
i dont understand the downvotes here. the point of any safety checker is to flag and ban potentially unsafe code, and force the author to rewrite with existing language patterns that guarantee the desired safety parameters. in this case, z
174.
by dnautics 3mo ago
intermediate representation. attempting to analyze zig code directly would be too hard (especially with comptime). on the way to the compiler backend, the compiler builds a simplified representation that only has "actually existing f
175.
by dnautics 3mo ago
i mean in zig-clr it pushes you towards more expressive patterns, for example, making you label pointers as optional if their status is ambiguous
176.
by dnautics 3mo ago
so yes it is possible to detect those patterns and ban them as unsafe, and have a"safety checked alternative. clr does this currently: https://github.com/ityonemo/clr#safety-oriented-architecture
177.
by dnautics 3mo ago
zig does have plans to give access to IRs when stable so adding a borrow checker to zig will be even easier than it is now
178.
by dnautics 3mo ago
Erlang's scheduler is not sophisticated, which is what makes it AWESOME. but yeah. i would be surprised if the JVM's scheduler is not more sophisticated than go's if for no other reason than it has way more knobs you can tu
179.
by dnautics 3mo ago
empirically untrue. several projects exist that bolt on extra safety to unsafe languages or unsafe parts of language. SeL4 for C, MIRI for rust unsafe. i guess ada/spark for ada too, is the OG, spark being added to ada 4 years after
180.
by dnautics 3mo ago
as a reminder its a construct in the zig stdlib to take an arbitrary chunk of memory (could be stack, could be in the programs static space) and wrap it in an allocator interface and give that to any data structure that needs an allocator a

More ›