You can put the use statement inside brackets (i.e. `{ use xyz ... }`) to limit the scope of the use statement.
I fully agree it's unexpected that everything after the use statement becomes part of the body of the use statement.
9,101 karma · joined July 1, 2010
I fully agree it's unexpected that everything after the use statement becomes part of the body of the use statement.
† pronounced "ch" as in "chase" of course, i.e. "trono"
This line lost the author a bit of benefit of my doubt. Certainly there is violence in those games, but they’re not particularly gory or murder-oriented. Seems like this article was written by and for people who have never played any video games.
To add some detail to this point:
> my understanding is that words in Chinese are largely monosyllabic and involve a decently high degree of homophones.
A syllabary would have had to represent phonetics as well as tones, which would have multiplied the required syllabary by n number of tones. For instance, Mandarin has 4 (or arguably 5) tones. The "ah" sound has four pronunciations: ā, á, ǎ, and à. Hong Kong Cantonese has at least 6 tones, having purportedly lost a few. Different dialects of Chinese have different numbers of tones, and some have been lost or gained within the same dialect throughout history.
1. That Chinese writing is inherently inefficient. It's actually very efficient...to read. And nothing beats the efficiency of having a script that maps perfectly to the language. Also as sibling comment notes, UTF-8 is a thing.
2. That there is no relation between written characters and phonetics. Incorrect, as several sibling comments point out.
3. That Japanese kana represents a successful "modernization" of kanji that Chinese should emulate.
4. That Chinese is "basically kanji" - assuming the Chinese and Japanese languages are essentially interchangeable. They...are not. I can't even begin to emphasize how much they are not. Chinese is subject-verb-object while Japanese is subject-object-verb, for instance. Chinese also has many phonemes that are incompatible with Japanese, which would not be covered in hiragana. Finally, kanji came from Chinese and has subtle differences and while it is mostly a subset of Chinese hanz, it has its own slightly different character set
> Kyber is an IND-CCA2-secure key encapsulation mechanism (KEM), whose security is based on the hardness of solving the learning-with-errors (LWE) problem over module lattices.
Curious to see if Chen's work will eventually lead to Signal selecting a different algorithm.
Great, lunar time hasn’t even been established and we already have two time zones.
We’ve had our first run ins with ticks in our suburban Chicago backyard recently. They were never an issue before, and never literally just outside the door. I’m sure the unseasonably warm start to the year is to blame.
> The paper is not on the internet yet.
And a followup tweet says:
> Yes repos were not public, paper was on Overleaf not the open Internet
> The real-world performance impact of bounds checks is surprisingly low.
> The greatest impact I’ve ever seen on real-world code from removing bounds checks alone was *15%,* but the typical gains are in *1% to 3% range,* and even that only happens in code that does a lot of number crunching.
> You can occasionally see greater impact (as we’ll see soon!) if removing bounds checks allows the compiler to perform other optimizations.
> Still, performance of code that’s not doing large amounts of number crunching will probably [not be impacted by bounds checks](https://blog.readyset.io/bounds-checks/) at all.
It is, of course, not universally applicable, so read the post for full details: https://shnatsel.medium.com/how-to-avoid-bounds-checks-in-ru...