matu3ba

11 ms·

61.
by matu3ba 3y ago
> the necessity of debt to measure and trade is dubious at best, selfish and evil at worst This is not what I wrote or meant, but I do agree that it could be understand like that. It would be of course better to measure necessity with so
62.
by matu3ba 3y ago
Unfortunately that is not how human nature works. Value itself depends on the necessity or desire of people for a product and is distributed via the money printing debt system. In other words: Necessary value can only exist, if other humans
63.
by matu3ba 3y ago
Can you tldr; the differences and corrections? arxiv has unfortunately nothing to show the errata.
64.
by matu3ba 3y ago
This sounds like a huge slowdown for linear memory access patterns (max. throughput), which do not fit into L1+L2 cache. I dont see options to prevent L3 cache time behavior being leaked unless one takes performance cuts for memory access p
65.
by matu3ba 3y ago
> Is there a fundamental reason we cannot make speculative execution secure? Any memory access leads to a time channel, which might be observable or not. As example, hyperthreading is known to create observable side channels even in L1 a
66.
by matu3ba 3y ago
One can check this via static analysis as the complete code tree can be inferred with relative ease (only package paths and usingnamespace are depending on comptime) + third party code will be able to query compiler info, so I do not expect
67.
by matu3ba 4y ago
At some point you would have to choose for which analysis you want unless you force the analysis onto everybody. Which means adding it into the build system. Which means separate commands. The nice thing is that Zig conventions make things
68.
by matu3ba 4y ago
Yes, this makes debug builds bloated and slow.
69.
by matu3ba 4y ago
> If zig supports compiler hooks, then it could conceivably halt compilation unless these invariants are satisfied. Can you sketch out why hooks are necessary on the proposals, like 14656 ? So far I have not read a justification, what th
70.
by matu3ba 4y ago
> more strongly typed alternatives See also this list for comparison https://github.com/fubark/cyber/issues/6 , if you dont want lua by a meta-compiler. If you want non-allocating scripting for optimal perf
71.
by matu3ba 4y ago
> How do I generate the required enthusiasm? Find a good use case that justifies using an unstable language. This is typically internal developer tooling or testing systems. Personally I would love a language with better type+test system
72.
by matu3ba 4y ago
What is better in an unfixable race condition (the time before the execve where stuff leaks)?
73.
by matu3ba 4y ago
so does posix_spawn, since you can leak file descriptors into parallel spawning threads/processes before the execve (where they are closed if having O_CLEXEC).
74.
by matu3ba 5y ago
> Yes, but why is this characterized as something negative? Unfortunately, the text does not provide sufficient context. Shell are not properly supported in any OS (probably except plan9), since 1. the OS provides no enforcement or conve
75.
by matu3ba 5y ago
The problem with implicit wrap-around of unsigned integer is that it makes your program slower. The underlying hardware with 2s complement does not need to pay the cost of reserving the overflow space or shifting/masking it out. Furthe
76.
by matu3ba 5y ago
I would like to bring up some counter-examples: - 1. Generators that can allocate prevent comptime-overapproximation of potential stack usage ( https://github.com/ziglang/zig/issues/157#issuecomment-76395... )
77.
by matu3ba 5y ago
The link to gmane does not work, since the content is only available via NNTP: http://news.gmane.io/ Do you have any backup etc?
78.
by matu3ba 5y ago
strace can have a significant overhead: https://www.brendangregg.com/blog/2014-05-11/strace-wow-much... What does the output of `perf trace` say?
79.
by matu3ba 5y ago
I would prefer something less broken than google docs. Something which can track semantic file changes in projects.
80.
Analysis of the overhead of a minimal Zig program(zig.news)
186 points by matu3ba 5y ago|107 comments
81.
by matu3ba 5y ago
The point I was trying to make is that you can get comparable guarantees, if you structure the code with atomticity + rollback and trace generalizations. Most people do not code like this due to missing language support for good error handl
82.
by matu3ba 5y ago
An effect system is redundant to code and is not free (compilation time cost) and neither helps when you dont know your future program spec or behavior. https://en.wikipedia.org/wiki/Effect_system It only prevents some
83.
by matu3ba 5y ago
Unfortunately the author is not very explicit on the interesting formal stuff: 1.implicit and 2.explicit proof-carrying code and 3. verifying compilers with its cost (there are as of today exactly 2 general usable and fully verified compile
84.
by matu3ba 5y ago
Drawing them could help figuring out all (invalid) state transitions. Certainly would make a cool drawing.
85.
by matu3ba 5y ago
The former (Inversion of Control) is a general method and too unspecific to answer. I can only hint that one of the biggest caveats of async is brittle composability due to missing cancellation routines. This will eventually be addressed. T
86.
by matu3ba 5y ago
> I don't see this specific threadpool doing anything to optimize for the disparate core clusters of your threadripper, or to acknowledge the disparity between core clusters on the M1. To do that efficiently you need to pin thread g
87.
by matu3ba 5y ago
not really legacy: https://en.wikipedia.org/wiki/Fortran#Science_and_engineerin... LAPACK upstream wont move to another language, unless there are significant advantages: https://en.wikipedia.org/wiki&#
88.
by matu3ba 5y ago
1. Union is used to dynamically interpret data of an underlying buffer or memory segment. You will find union as being inherently unsafe in Rust: https://doc.rust-lang.org/reference/items/unions.html 2. petgraph l
89.
by matu3ba 5y ago
1. Rust doesnt let you safety-check bit-compressed stuff and instead relies on well-formed types during runtime (basically everything that union allows). 2. Graph memory patterns in Rust are completely unsafe. 3. Code might leak and you don
90.
by matu3ba 5y ago
As of now the tradeoff of Rust's type system is that code may leak memory and you may need to investigate all occurrences to fix it, because there is no tooling yet (testing everything is infeasible). You can have either extensive stat

More ›