91–100 of 203 posts
Earlier quoted context omitted.
I mean, this would be relatively easy to implement in any language that have operator overloading.
How do you operator overload in C++ so that calling computeHmac(secret(string)) returns secret(string)?
Then define the equals operator for "secret" to behave in the needed way.
The former is trivial to implement in Rust and C++, the latter is a bit more complicated, but also implementable in both via macros, in a reasonably ergonomic way.
What is the advantage then?
Oh good, maybe it’ll be here a while.
Implicit nullability of all values, a very dubious design decision in a new language.
Given that they mention SQL more than other things, and stress SoA and memory intensive applications, I think this makes more sense than it would otherwise
I'm not convinced that implicit nullability is a good idea, either in SQL or in newly designed languages.
I don't see the connection between implicit nullability and SoA. If you have a link to some example, that would be interesting to read.
Earlier quoted context omitted.
The code is owned by Google because it was written by a Google employee on the job.
Or off the job -- Google claims ownership either way. https://news.ycombinator.com/item?id=1969979
Earlier quoted context omitted.
Ah, so they're repeat offenders. How's it go again? Cache invalidation, naming tconcurrencyhings, , and off-by-one errors?
Google: - leader in AI and text generation - unable to find or create original names for langs
Can someone explain how this works: "Assume the attacker can tell how long it takes for mac == computedMac to run. If the first byte of an attacker-chosen mac is wrong for the attacker-chosen message, the loop terminates after just one comparison. With 256 attempts, the attacker can find the first byte of the expected MAC for the attacker-controlled message. Repeating this process, the attacker can forge an entire MA…
timing safe means always using the full loop and not branching away on certain values. every value needs the same time.
x^2 means x squared, orphaning the XOR operator. Rune is for crypto, so math comes first.
There already exists Rune programming language and that one was earlier: https://rune-rs.github.io/ They should be more careful picking the name.
Earlier quoted context omitted.
There already was a GO programming language before Google decided to use the name, too.
That doesn't justify them choosing an already chosen name now, does it?
There is nothing nefarious here. There is no cabal. These things happen all the time. I've had it happen to two of my own small/obscure projects. It happens.