> Writing rules, or steps, unambiguously in a high level language and having those statements translated to lower level languages, that ultimately get executed by a machine, is what compilers do.
And it definitely is not what LLMs do, even if you pepper your rules with “NEVER, ever deviate from these rules”.
Also, when left-handed writing became accepted, there were special left handed pens (with a broader tip that you can push forward without it ‘biting’ into the paper)
Finally, how do you know nobody did that, and got harassed for writing incorrectly?
“Particularly when produced spontaneously, mirror writing is a highly heterogeneous phenomenon: the mirroring may range from as small an item as a single reversed letter, through numerous reversed letters but not words, to thousands of pages of mirrored script; the place in the word in which a mirror letter occurs is variable, and numerals may or may not be reversed too”
My father was a southpaw, but he wrote with his right hand, because when he was in primary school, before WWII, he got his hand beaten many times, to encourage him to write only with the right hand.
Except for writing, for everything else requiring skill he used his left hand.
“What may be the first documented reference to the character is a 1937 maintenance manual from the Teletype Corporation, which includes a photograph showing the keyboard of its Kleinschmidt keyboard perforator WPE-3 using the Wheatstone system. In a 1945 document, Teletype used the name "diagonal key" for the symbol, and gives it a (non-standard) Morse code of ._.._ . Neither document gives its usage”
> If a left handed person does it, its been invented beforehand
I disagree. A left-handed person writing a slash in mirror image doesn’t write a backslash; they write a slash using a different glyph.
There are some fascinating theories on how writing media affects writing direction and glyph shape. A lot of southeast asian languages have a lot of curves/circles because they'd use a stylus on a banana leaf and the curves are less likely to run a split in the leaf.
> I don't see where in the memory map there would even be enough space for a screen buffer that large to be located
1024 × 600 with 256 colours is 600 kB. Even in monochrome, it would be over 64 kB.
> but it looks like the LCD has to be bit banged by the CPU data bus directly?
Even at 20 Hz, that would involve writing over a ten million pixels per second, giving you about 1 CPU cycle per pixel ⇒ there’s no way to do that with this CPU.
“In a paper published in 2016, “The first proof of the recent presence of Wolves in the Netherlands,” authors wrote:
“In light of the expansion of wolves from the Polish border to the northwest of Germany and the sightings in Denmark, the appearance of the wolf in the Netherlands was no surprise to most experts. In March 2015, this expectation was fulfilled when, after generations without resident wolves, a single wolf wandered through the Dutch provinces of Drenthe and Groningen in broad daylight. From 7 to 10 March 2015, the Netherlands witnessed the comeback of an iconic species.”
Since 2019, the country has once again become home to its first pack of wolves with young pups after 150 years. Genetic sampling revealed the Netherlands wolves came from an Alpine population and Central European populations (i.e. Germany)“
No, but a trillion dollar company going to a ratings agency to get an assessment of its credit rating and not giving that ratings agency enough information to do that doesn’t inspire confidence in that trillion dollar company, either.
Why didn’t they give them the info? They either withheld it or don’t have it. Both make them look bad.
> But the base model will just be a regular Tesla.
A regular Tesla that sucks, you mean?
Even the base model has “active aerodynamics and a multi-mode suction system that maximizes downforce for next-level performance on and off the track.”
I haven't tried it and am afk rn but I'd imagine you just define a constexpr function that implements collatz and use that in your contract.
(Edit: if the input is constexpr itself)
Its also quire easy to think about specializing a few templates and doing it that way. If you look up an example of the fib sequence in c++ templates you'll get the general idea.
I feel like I'd have something to learn from seeing the code.
Won't you just run into a constexpr evaluation depth error with a suggestion to set -fconstexpr-depth? I don't see how this is the gotcha it's made out to be.
I'd exepct something like that to happen. Worth reiterating that the whole scenario is for a hypothetical different implementation of contract that would execute comptime, as noted in the parent thread.
If you wanted a c++26 preconditon for collatz tho, here it is.
```cpp
bool collatz(unsigned long long n) {
while (n != 1) n = n % 2 ? 3 * n + 1 : n / 2;
return true;
}
void f(unsigned long long n) pre(collatz(n));
```
That's basically what you'd write if you were doing it with asserts, as the linked article states, just now you add it to the declaration.
And it definitely is not what LLMs do, even if you pepper your rules with “NEVER, ever deviate from these rules”.
reply