On Fri, 19 Jun 2020 20:30:03 +0100
Barry Scott wrote:
>
> > I know very little about how this works except a vague rule of thumb
> > that in the 21st century memory locality is king. If you want code to be
> > fast, keep it close together, not spread out.
>
> Remember that the caches are
On Sun, Jun 21, 2020 at 02:53 M.-A. Lemburg wrote:
> On 21.06.2020 01:47, Guido van Rossum wrote:
> > Hm, I remember Greg's free threading too, but that's not the idea I was
> > trying to recall this time. There really was something about bytecode
> > objects being loaded from a read-only
On 21.06.2020 01:47, Guido van Rossum wrote:
> Hm, I remember Greg's free threading too, but that's not the idea I was
> trying to recall this time. There really was something about bytecode
> objects being loaded from a read-only segment to speed up code loading.
> (Much quicker than
On Sun, 21 Jun 2020 11:07:05 +0200
Antoine Pitrou wrote:
>
> There's no such thing as "the cache". There are usually several levels
> of cache. L1 cache is closest to the CPU [...]
... Note by "closest to the CPU" I really mean "closest to the CPU
core's execution units". Those caches are
I'm just curious if there was a reason why Boolean was omitted from the
numeric tower in the numbers library? It seems that builtins.bool and
numpy.bool_ would both be elements of Boolean, and Boolean itself would be
Integral?
Best,
Neil
___
