This reminds me of being in secondary school and procrastinating/nerd sniping our teacher for A-level Further Maths (so I was roughly 17-18) by arguing that a number system in base e (so 1, 2, 2.1, ..., 2.7, 2.71, ..., 10) would simplify a lot of the maths we were studying.
Except that's not how bases work. The digits would be of the form e^n. See [1]. Since e is not an integer, its number system uses 3 symbols (0, 1, 2) as 3 is bigger than e. Thus, 20 = 2e^1 + 0e^0 = 5.43656...
I don't know about simplify. Subtracting 1 from the above would yield an irrational number. So certainly not useful for arithmetic. How about for mathematical proofs? Well, any integer above 3 is also irrational. Makes Taylor series annoying. Even mundane things like the factorial would not have a nice representation.
> a number system in base e (so 1, 2, 2.1, ..., 2.7, 2.71, ..., 10)
I don't think I understand the significance of those dots. How would one write, say, 100 in this number system?
With that said, the usual "base" notation works perfectly well for non-integer radices, though it can behave in unexpected fashion. Thus, I might write 12012 for e^4 + 2e^3 + e + 2, which is approximately 99.49, and so can be regarded as the "e-adically integer" part of 100.
> A few other oligarchs, and their companies, have been exempted because of their importance to the global commodities market, most notably Oleg Deripaska and his aluminium producer Rusal.
> When very harsh sanctions were imposed on Deripaska in 2018 that effectively banned doing any business with the company, prices for aluminium on the London Metals Exchange (LME) soared by 40% overnight potentially causing a price shock for the consumers of the metal. The implementation of those sanctions were at first delayed and eventually withdrawn completely
It has felt to me over the last few years (and I have no inside knowledge) that Google Maps saw Apple Maps fail at launch, and didn't improve the service at all.
Meanwhile, Apple Maps and the OpenStreetMaps backing data has continued to get better and better each year.
One core place that shorting is key (which isn't touched on much) is shorting/going long on commodity futures. Very simplified example below:
If I'm an airline (and my business is dependent on the price of oil) and I think the price of oil will go up, I will hold some amount of oil futures at the current price. If the price of oil rises, my company is "hedged" against that rise. This is good for the buyer of the commodity. If the price of oil goes down, I lose on my future, but my business is fine overall.
Correspondingly, if I'm the seller of a commodity (I own an oilfield), I might short oil futures, in case the price goes down. I make less money selling my oil, but I hopefully make some back on the short
If the result of my `sort ` function is dependent on `sizeof(void )` being 8, when I compile from my x86 hardware for a 32-bit only architecture, assumptions go awry.
Note that this isn't likely with something like sort, but definitely is* likely with precomputing values/structs etc.
