<oystewh>
trying to get cl-async to work on mac, but it stalls on some compilation because cffi/grovel/whatever-it-is uses /usr/bin/clang rather than the one installed through macports (and appropriately added to the path). any ideas for a good fix?
<White_Flame>
symlink?
<oystewh>
too dirty a fix.. might break something else
z147x has quit [Quit: z147x]
turona_ has joined #lisp
Codaraxis has joined #lisp
turona has quit [Ping timeout: 256 seconds]
Lord_of_Life_ has joined #lisp
slyrus_ has joined #lisp
Lord_of_Life has quit [Ping timeout: 268 seconds]
Lord_of_Life_ is now known as Lord_of_Life
slyrus has quit [Ping timeout: 272 seconds]
slyrus__ has joined #lisp
v_m_v has quit [Remote host closed the connection]
slyrus_ has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 240 seconds]
slyrus_ has joined #lisp
georgiePorgie has joined #lisp
slyrus__ has quit [Ping timeout: 240 seconds]
fivo has quit [Quit: WeeChat 1.9.1]
Codaraxis has quit [Read error: Connection reset by peer]
brandelune has joined #lisp
oxum has quit [Ping timeout: 272 seconds]
Bike has joined #lisp
oxum has joined #lisp
slyrus__ has joined #lisp
oxum has quit [Ping timeout: 268 seconds]
slyrus_ has quit [Ping timeout: 272 seconds]
Codaraxis has joined #lisp
oxum has joined #lisp
oxum has quit [Ping timeout: 260 seconds]
v88m has joined #lisp
pjb has quit [Read error: No route to host]
pjb has joined #lisp
ebzzry has joined #lisp
Codaraxis has quit [Read error: Connection reset by peer]
Codaraxis has joined #lisp
gko_ has joined #lisp
lavaflow has quit [Ping timeout: 240 seconds]
marusich has joined #lisp
kim\ has joined #lisp
bitmapper has quit [Ping timeout: 268 seconds]
georgiePorgie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Codaraxis has quit [Remote host closed the connection]
Codaraxis has joined #lisp
nullniverse has joined #lisp
_whitelogger has joined #lisp
pjb has quit [Remote host closed the connection]
igemnace has joined #lisp
pjb has joined #lisp
space_otter has joined #lisp
dddddd has quit [Ping timeout: 256 seconds]
jeosol has quit [Remote host closed the connection]
ebzzry has quit [Ping timeout: 272 seconds]
Codaraxis has quit [Read error: Connection reset by peer]
lavaflow has joined #lisp
gnufr33d0m has joined #lisp
ebrasca has quit [Remote host closed the connection]
PuercoPope has quit [Remote host closed the connection]
pjb has quit [Remote host closed the connection]
pjb has joined #lisp
gko_ has quit [Ping timeout: 256 seconds]
rwcom has joined #lisp
FreeBirdLjj has joined #lisp
buffergn0me has joined #lisp
oxum has joined #lisp
buffergn0me has quit [Ping timeout: 240 seconds]
Ukari has quit [Remote host closed the connection]
Ukari has joined #lisp
oxum has quit [Remote host closed the connection]
oxum has joined #lisp
FreeBirdLjj has quit [Remote host closed the connection]
FreeBirdLjj has joined #lisp
pjb has quit [Ping timeout: 240 seconds]
v88m has quit [Ping timeout: 272 seconds]
brandelune has quit [Quit: This computer has gone to sleep]
FreeBirdLjj has quit [Ping timeout: 256 seconds]
pjb has joined #lisp
Oladon has joined #lisp
oldtopman has quit [Quit: *poof*]
oldtopman has joined #lisp
FreeBirdLjj has joined #lisp
Codaraxis has joined #lisp
oldtopman has quit [Quit: *poof*]
oldtopman has joined #lisp
nullman has quit [Ping timeout: 260 seconds]
gravicappa has joined #lisp
nullman has joined #lisp
ggole has joined #lisp
wxie has joined #lisp
shangul has joined #lisp
Josh_2 has joined #lisp
v88m has joined #lisp
gnufr33d0m has quit [Quit: gnufr33d0m]
gko_ has joined #lisp
taof has joined #lisp
brandelune has joined #lisp
Guest19180 has joined #lisp
megalography1 has left #lisp [#lisp]
Guest19180 has quit [Ping timeout: 272 seconds]
akoana has joined #lisp
Bike has quit [Quit: Lost terminal]
wxie has quit [Ping timeout: 240 seconds]
wxie has joined #lisp
pjb has quit [Remote host closed the connection]
pjb has joined #lisp
hsaziz has joined #lisp
froggey has quit [Ping timeout: 265 seconds]
froggey has joined #lisp
brandelune has quit [Ping timeout: 265 seconds]
Codaraxis has quit [Remote host closed the connection]
Codaraxis has joined #lisp
hsaziz has quit [Quit: hsaziz]
igemnace has quit [Quit: WeeChat 2.7]
shifty has joined #lisp
shifty has quit [Ping timeout: 240 seconds]
ebzzry has joined #lisp
georgiePorgie has joined #lisp
sauvin has joined #lisp
Josh_2 has quit [Ping timeout: 240 seconds]
hsaziz has joined #lisp
hsaziz has quit [Client Quit]
Nilby has joined #lisp
xkapastel has joined #lisp
taof has quit [Remote host closed the connection]
vlatkoB has joined #lisp
libertyprime has joined #lisp
narimiran has joined #lisp
Oladon has quit [Quit: Leaving.]
<beach>
Good morning everyone!
FreeBirdLjj has quit [Remote host closed the connection]
georgiePorgie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Josh_2 has joined #lisp
marusich has quit [Quit: Leaving]
gnufr33d0m has joined #lisp
gnufr33d0m has quit [Remote host closed the connection]
gko_ has quit [Ping timeout: 240 seconds]
dale has quit [Quit: My computer has gone to sleep]
shka_ has joined #lisp
nullniverse has quit [Ping timeout: 272 seconds]
shka_ has quit [Ping timeout: 240 seconds]
ebzzry has quit [Read error: Connection reset by peer]
McParen has joined #lisp
brandelune has joined #lisp
wxie has quit [Ping timeout: 240 seconds]
Nilby has left #lisp ["👽愛🆑"]
Nilby has joined #lisp
brandelune has quit [Quit: This computer has gone to sleep]
FreeBirdLjj has joined #lisp
FreeBirdLjj has quit [Remote host closed the connection]
FreeBirdLjj has joined #lisp
orivej has joined #lisp
FreeBirdLjj has quit [Ping timeout: 240 seconds]
brandelune has joined #lisp
libertyprime has quit [Ping timeout: 260 seconds]
libertyprime has joined #lisp
nika has joined #lisp
karlosz has joined #lisp
shangul has quit [Read error: Connection reset by peer]
mangul has joined #lisp
frodef has joined #lisp
reverse_light has joined #lisp
v_m_v has joined #lisp
mangul is now known as shangul
brandelune has quit [Quit: This computer has gone to sleep]
v_m_v has quit [Ping timeout: 268 seconds]
libertyprime has quit [Ping timeout: 260 seconds]
libertyprime has joined #lisp
brandelune has joined #lisp
brandelune has quit [Ping timeout: 260 seconds]
terpri has quit [Ping timeout: 260 seconds]
georgiePorgie has joined #lisp
terpri has joined #lisp
brandelune has joined #lisp
shangul has quit [Ping timeout: 240 seconds]
karlosz has quit [Remote host closed the connection]
brandelune has quit [Quit: This computer has gone to sleep]
shangul has joined #lisp
space_otter has quit [Remote host closed the connection]
X-Scale` has joined #lisp
X-Scale has quit [Ping timeout: 265 seconds]
X-Scale` is now known as X-Scale
rippa has joined #lisp
karlosz has joined #lisp
Guest19180 has joined #lisp
random-nick has joined #lisp
Guest19180 has quit [Ping timeout: 272 seconds]
nika_ has joined #lisp
nika has quit [Ping timeout: 240 seconds]
v88m has quit [Ping timeout: 256 seconds]
narimiran has quit [Ping timeout: 272 seconds]
varjag has joined #lisp
nika_ has quit [Read error: Connection reset by peer]
cosimone has joined #lisp
nika has joined #lisp
brandelune has joined #lisp
zaquest has quit [Quit: Leaving]
libertyprime has quit [Ping timeout: 272 seconds]
libertyprime has joined #lisp
dddddd has joined #lisp
georgiePorgie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Josh_2>
can I redirect *error-output* to a file? I keep getting an error flash up but not long enough to read it
zaquest has joined #lisp
v_m_v has joined #lisp
georgiePorgie has joined #lisp
mangul has joined #lisp
shangul has quit [Read error: Connection reset by peer]
xkapastel has quit [Quit: Connection closed for inactivity]
mangul has quit [Read error: Connection reset by peer]
notzmv has quit [Ping timeout: 260 seconds]
shangul has joined #lisp
Ven`` has joined #lisp
igemnace has joined #lisp
shangul has quit [Quit: Leaving]
<beach>
Josh_2: Sure.
<LdBeth>
sure, just bind a file io to that variable
<LdBeth>
hello beach
<beach>
Hey LdBeth.
<Josh_2>
LdBeth: how do I do that
shangul has joined #lisp
ebzzry has joined #lisp
<LdBeth>
Josh_2: (with-open-file (*error-output* #P"path/to/file") body ...)
<Josh_2>
Okay thanks :)
rwcom7 has joined #lisp
nika has quit []
rwcom has quit [Ping timeout: 260 seconds]
rwcom7 is now known as rwcom
Ven`` has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
gko_ has joined #lisp
Nilby has left #lisp ["👽愛🆑"]
patrixl has quit [Quit: Leaving.]
igemnace has quit [Quit: WeeChat 2.7]
libertyprime has quit [Quit: leaving]
shangul has quit [Ping timeout: 240 seconds]
shifty has joined #lisp
papachan has joined #lisp
dddddd has quit [Ping timeout: 260 seconds]
lucasb has joined #lisp
shifty has quit [Ping timeout: 240 seconds]
shifty has joined #lisp
Lord_of_Life_ has joined #lisp
akoana has left #lisp ["Leaving"]
shifty has quit [Ping timeout: 260 seconds]
shifty has joined #lisp
Lord_of_Life has quit [Ping timeout: 260 seconds]
Lord_of_Life_ is now known as Lord_of_Life
ebzzry has quit [Ping timeout: 256 seconds]
HiRE has quit [Quit: Later]
HiRE has joined #lisp
scymtym has joined #lisp
v_m_v has quit [Remote host closed the connection]
<pjb>
LdBeth: the only streams it's not advised to redirect are *terminal-io* and *debug-io*…
shifty has quit [Ping timeout: 240 seconds]
shifty has joined #lisp
<p_l>
and I'd say that it's more "don't do this till you know how to do it safely"
X-Scale` has joined #lisp
X-Scale has quit [Ping timeout: 240 seconds]
X-Scale` is now known as X-Scale
Nilby has joined #lisp
cosimone has quit [Quit: Terminated!]
Bike has joined #lisp
<Nilby>
for be like me and forget you redirected the debugger to another window and kill it only to realize later it was waiting patiently to be debugged
<Nilby>
*or
shifty has quit [Ping timeout: 260 seconds]
shifty has joined #lisp
karlosz has quit [Quit: karlosz]
Guest19180 has joined #lisp
oystewh has left #lisp ["."]
Guest19180 has quit [Ping timeout: 240 seconds]
McParen has quit [Ping timeout: 272 seconds]
shifty has quit [Ping timeout: 240 seconds]
papachan has quit [Ping timeout: 256 seconds]
shifty has joined #lisp
georgiePorgie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
amerlyq has joined #lisp
davsebamse has quit [Ping timeout: 268 seconds]
shifty has quit [Ping timeout: 240 seconds]
shifty has joined #lisp
shangul has joined #lisp
cosimone has joined #lisp
shifty has quit [Ping timeout: 240 seconds]
shifty has joined #lisp
amerlyq has quit [Quit: amerlyq]
jmercouris has joined #lisp
rwcom2 has joined #lisp
stepnem_ has quit [Read error: Connection reset by peer]
rwcom has quit [Ping timeout: 240 seconds]
rwcom2 is now known as rwcom
georgiePorgie has joined #lisp
shifty has quit [Ping timeout: 260 seconds]
stepnem has joined #lisp
shifty has joined #lisp
jmercouris has quit [Remote host closed the connection]
Ven`` has joined #lisp
shifty has quit [Ping timeout: 260 seconds]
stzsch has quit [Ping timeout: 252 seconds]
ebzzry has joined #lisp
narimiran has joined #lisp
FreeBirdLjj has joined #lisp
davsebamse has joined #lisp
cosimone has quit [Quit: Terminated!]
<LdBeth>
do you all keep up to date with latest lisp version?
<Nilby>
I know. I get a bit sad every time I try doing a round of portability checks.
FreeBirdLjj has quit [Remote host closed the connection]
FreeBirdLjj has joined #lisp
<oni-on-ion>
does CL have any other remaining features after portability becomes mythical?
<Nilby>
Shinmera: Thanks for doing that grid. It's very useful.
<Shinmera>
Sure. Just wish it was more accurate and kept better up to date :)
<ebrasca>
oni-on-ion: Some parts are better if they have portability.
georgiePorgie has joined #lisp
FreeBirdLjj has quit [Ping timeout: 268 seconds]
<oni-on-ion>
hmm
lemoinem has quit [Ping timeout: 260 seconds]
georgiePorgie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
whiteline has quit [Quit: Leaving]
lemoinem has joined #lisp
whiteline has joined #lisp
<ebrasca>
oni-on-ion: What do you do with usocket wichout portability?
asarch has joined #lisp
georgiePorgie has joined #lisp
Necktwi has quit [Ping timeout: 240 seconds]
nowhere_man has joined #lisp
dddddd has joined #lisp
brandelune has quit [Quit: This computer has gone to sleep]
Necktwi has joined #lisp
gnufr33d0m has joined #lisp
orivej has quit [Ping timeout: 272 seconds]
nullniverse has joined #lisp
nowhere_man has quit [Ping timeout: 260 seconds]
CrazyPython has joined #lisp
z147 has joined #lisp
hiroaki has quit [Ping timeout: 272 seconds]
Guest19180 has joined #lisp
gnufr33d0m has quit [Quit: gnufr33d0m]
georgiePorgie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Guest19180 has quit [Ping timeout: 260 seconds]
bitmapper has joined #lisp
gko_ has quit [Ping timeout: 256 seconds]
CrazyPython has quit [Read error: Connection reset by peer]
narimiran has quit [Ping timeout: 256 seconds]
Oladon has quit [Quit: Leaving.]
narimiran has joined #lisp
whiteline has quit [Read error: Connection reset by peer]
whiteline has joined #lisp
Inline has joined #lisp
shangul has quit [Ping timeout: 240 seconds]
ebrasca has quit [Remote host closed the connection]
Nilby has quit [Read error: Connection reset by peer]
Nilby has joined #lisp
dale has joined #lisp
notzmv has joined #lisp
pfdietz has joined #lisp
asarch has quit [Quit: Leaving]
bitmapper has quit [Ping timeout: 260 seconds]
shangul has joined #lisp
varjag has quit [Remote host closed the connection]
Ven`` has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Ven`` has joined #lisp
Ven`` has quit [Client Quit]
Guest19180 has joined #lisp
z147 has quit [Remote host closed the connection]
z147 has joined #lisp
Guest19180 has quit [Ping timeout: 240 seconds]
karlosz has joined #lisp
Fade has quit [Read error: Connection reset by peer]
McParen has joined #lisp
gravicappa has quit [Ping timeout: 272 seconds]
hiroaki has joined #lisp
Fade has joined #lisp
z147 has quit [Remote host closed the connection]
z147 has joined #lisp
bitmapper has joined #lisp
cosimone has quit [Quit: Quit.]
ggole has quit [Quit: Leaving]
shangul has quit [Ping timeout: 265 seconds]
v88m has quit [Ping timeout: 272 seconds]
CrazyPython has joined #lisp
shangul has joined #lisp
wsinatra_ has joined #lisp
EvW has joined #lisp
shangul has quit [Ping timeout: 256 seconds]
Jesin has quit [Quit: Leaving]
ebzzry has joined #lisp
Jesin has joined #lisp
rippa has quit [Quit: {#`%${%&`+'${`%&NO CARRIER]
varjag has joined #lisp
ebzzry has quit [Ping timeout: 268 seconds]
shka_ has joined #lisp
reverse_light has quit [Remote host closed the connection]
cosimone has joined #lisp
z147 has quit [Remote host closed the connection]
z147x has joined #lisp
buffergn0me has joined #lisp
CrazyPython has quit [Ping timeout: 240 seconds]
shka_ has quit [Ping timeout: 268 seconds]
wsinatra_ has quit [Quit: WeeChat 2.7]
slac-in-the-box has joined #lisp
Codaraxis has quit [Ping timeout: 268 seconds]
<aeth>
I'm sure a lot of code implicitly assumes 64-bit, while the standard back in 1994 sets its minimum requirements such that even 16-bit implementations are possible. e.g. Any docstring larger than 1024 is technically non-conforming because strings are just arrays and ARRAY-TOTAL-SIZE-LIMIT can be as low as 1024.
<aeth>
And it would be pretty irrational to code for a hypothetical implementation with 1024-max-sized-strings when nearly everyone's using 64-bit implementations and all of the rest are using 32-bit implementations.
<aeth>
If you code for 64-bit implementations, then it still runs in 32-bit, but slower. If you code for maximum portability, then you have to spend a lot of time working around limits like 1024-length arrays that you could reasonably run into in your program, for the benefit of 0 users.
<pjb>
However, 32-bit limitations are often too small too. Therefore it would not be entirely idiotic to use a library to wrap limited data structures in extended data structure on small implementations.
<oni-on-ion>
so the best is dynamic-bit system ?
<pjb>
However, with such a library, #\" would have to read long string literals as a different data type, that could not be used with cl:documentation.
<aeth>
pjb: Yes, but the 32-bit limitations are usually 512 MB to 4 GB (probably not 4 GB because of tag bits), so they're much harder to reach (though possible)
<pjb>
On the other hand, those limitations exist because of actual physical memory space limitations, so it wouldn't be bad to issue a warning and store them on disk.
shangul has joined #lisp
<pjb>
But you're right that with time passing, this becomes less and less of a problem, unless you want to write lisp code for Arduino or ESP32…
CrazyPython has joined #lisp
<aeth>
pjb: You probably can do a space-extending trick about 4 times because of tag bits meaning you can't allocate up to the maximum memory limitations (assuming that the system is at the maximum the platform can support!). At the very least a bit under twice, but probably a bit under three times.
Codaraxis has joined #lisp
<aeth>
If you're doing typical tag bits, at best you can do what 64-bit SBCL does and have 1 tag bit, but that's a signed integer, so it's like effectively losing 2 bits for positive numbers. So a limit of e.g. 4 GB for 32-bit would become 1 GB at best (even 32-bit SBCL doesn't do things this way, unlike 64-bit SBCL, though!), even if you have 4 GB RAM available.
<aeth>
So, actually, correction, you could do this space extension 4x
<froggey>
tag bits are typically stored in the low bits, not the high bits, so they don't take away from the maximum supported memory
<aeth>
froggey: Right, but my point is you probably cannot e.g. have an array the size of the maximum supported memory because of ARRAY-TOTAL-SIZE-LIMIT
<aeth>
froggey: And pjb's point was (afaik) to wrap around that, e.g. an array of size 4 or a list of size 4 that extends an array to reach the memory limit
gravicappa has joined #lisp
<froggey>
oh, right. I missed the bit about A-T-S-L
Khisanth has quit [Ping timeout: 256 seconds]
<aeth>
My original point is that this is something no one thinks about because people mostly implicitly write for 64-bit (where this won't be an issue for 10-15 years, and even then only on huge servers) instead of portably. Of course, most 64-bit code will run on 32-bit implementations, just slower (e.g. boxed single-floats and bignum (unsigned-bit 64)s) and the real issue is when you want full portability to e.g. max-size-1024 arrays.
CrazyPython has quit [Read error: Connection reset by peer]
<pfdietz>
There are other places where programs make assumptions that go beyond the standard. A common one is to assume that standard functions that return boolean will return T for true.
<pjb>
(log (expt 2 64) 10) #| --> 19.26592 |#
<aeth>
pfdietz: That seems justifiable to me. The type BOOLEAN is T or NIL.
McParen has left #lisp [#lisp]
<pjb>
If it returns booleans, you should. But most return generalized booleans, not booleans.
<pfdietz>
Yes, but for almost all such functions they are described as returning a "generalized boolean".
saravia has joined #lisp
<pfdietz>
WHich means, any damn thing they want for true, except nil.
<pfdietz>
I had wrap so many expressions in (notnot ...) in ansi-tests.
Guest19180 has joined #lisp
<aeth>
pfdietz: well, generalized boolean is different, and is effectively describing (NOT NULL)
<aeth>
I'm not sure where people assume T but get (NOT NULL) though. Probably in some places
<pfdietz>
The point being, programs often assume the implementation will return T for true, because most will do that.
<aeth>
pfdietz: oh I see, stuff like NUMBERP are described as returning generalized-boolean so (numberp 42) could plausibly return 42
<pfdietz>
One place this comes up is in (typep x '(member ...)). If that translates to a call to MEMBER, then T is not the returned value for true.
<pfdietz>
Some implementations returns different values there depending on optimization settings.
<aeth>
weird
<pfdietz>
BTW, if you want a mostly pointless efficiency hack: it's faster to return 0 and check for eql to that, instead of checking for eq to NIL. The object code is more compact. Lousy style, of course.
<pfdietz>
(this is in user code; standard fns cannot do that)
Guest19180 has quit [Ping timeout: 265 seconds]
Khisanth has joined #lisp
<Nilby>
but then there's digit-char-p
<aeth>
I'm not sure why that's digit-char-p and not digit-char
<aeth>
It seems like a mistake to have -P when its return is potentially meaningful
<Nilby>
I'm guessing historical reasons.
orivej has joined #lisp
<TMA>
I would guess that the non-"-P" alternative would suggest the return value is undefined (or useless) for non-digit characters
buffergn0me has quit [Ping timeout: 256 seconds]
<pjb>
aeth: history.
gravicappa has quit [Ping timeout: 240 seconds]
pfdietz has left #lisp [#lisp]
ebrasca has joined #lisp
ArthurStrong has joined #lisp
cartwright has quit [Remote host closed the connection]
slac-in-the-box has quit [Remote host closed the connection]
terpri has quit [Read error: Connection reset by peer]
nowhere_man has joined #lisp
jmercouris has joined #lisp
slac-in-the-box has quit [Remote host closed the connection]
EvW has quit [Ping timeout: 256 seconds]
narimiran has quit [Ping timeout: 272 seconds]
lucasb has quit [Quit: Connection closed for inactivity]
ArthurStrong has quit [Quit: leaving]
v_m_v has joined #lisp
ebrasca has quit [Remote host closed the connection]
nowhere_man has quit [Ping timeout: 272 seconds]
torbo has joined #lisp
orivej has quit [Ping timeout: 265 seconds]
ebrasca has joined #lisp
koenig has quit [Quit: WeeChat 2.5]
orivej has joined #lisp
<aeth>
pjb: yeah, now show the version of that photo but with RAM... and compare the price tag, too :-p
Ven`` has joined #lisp
zooey has quit [Remote host closed the connection]
zooey has joined #lisp
<pjb>
aeth: they're SSD, almost as good as RAM.
<pjb>
aeth: just consider the SD-RAM as L3 cache.
Oladon has joined #lisp
<aeth>
Although, actually to be fair, my bad, 4 PB is the limit of AMD64 (actually 256 TB until it's raised, but it is raisable), but not 64-bit in general. 4 PB is 2^52 and should be a fixnum in most 64-bit implementations. And that's the limit that will potentially be reached "soon" (10-15 years?) for very high end servers.
<aeth>
AMD is 6 doublings away from reaching the temporary limit in AMD64's architecture (from 4 TB for EPYC 2 to 256 TB)... and then if I did my LOG ... 2 correctly they're 10 capacity doublings away from the overall platform limit for AMD64.
<aeth>
And that's 12 doublings less than what 64-bit as a whole could address in theory...
<aeth>
Quite a few tag bits (11) permitted for fixnums on at least x86-64, the most popular 64 bit.
<aeth>
(As far as making e.g. an array the size of memory.)
swills has quit [Ping timeout: 272 seconds]
rozenglass has quit [Read error: Connection reset by peer]
<aeth>
I'm guessing that 6 doublings means they'll raise the architectural limit to its theoretical max in 6-12 years (although Intel might be ahead of AMD here) and then it's 4-8 more years before they might have to do something more drastic (if that's even possible). And even then, it would only affect very large servers, like you might see in cloud computing.
Guest19180 has joined #lisp
cl-arthur has joined #lisp
<Nilby>
or just set the terminal to infinite scrollback and compile sbcl, 4PB easy
Guest19180 has quit [Ping timeout: 240 seconds]
<aeth>
Nilby: well, I mean, if it's *infinite* scrollback...
<Nilby>
perhaps I should have said "unlimited", which we know is in practice always less than most-positive-fixnum
xkapastel has joined #lisp
<aeth>
Oh, and fwiw in SBCL (log array-total-size-limit 2) => 62.0 which is the maximum it can be with 1 tag bit on the fixnum (because fixnums are signed) which is more than the 4 PB (2^52) that x86-64 can have as its memory. I wonder if there's a 64-bit platform where that's not enough, though. Or if x86-64 could one day be extended so that that's not enough. Not really an issue for the next 20 years, probably.
u0_a121 has joined #lisp
<aeth>
For "ARM architecture" on Wikipedia, it says "Memory translation from 48-bit virtual addresses based on the existing Large Physical Address Extension (LPAE), which was designed to be easily extended to 64-bit." which I guess means that for ARM it's 2^48 (exactly the same as the current x86-64) and eventually will be 2^64 (unlike the eventual 2^52 for x86-64)
jmercouris has quit [Ping timeout: 272 seconds]
<Nilby>
There must be a better way than pushing so many electrons around.
<aeth>
This is a lot of text to say that "limits don't matter on 64-bit implementations even in the decade of the 2020s", though. At least 2-3 decades of programming without having to think about architectural limits. 64 bit has been a bit magical in that sense.
slyrus_ has joined #lisp
<aeth>
Nilby: As far as the language is concerned, I don't think it cares exactly what it runs on?
Nilby has quit [Read error: Connection reset by peer]
u0_a121 has quit [Read error: Connection reset by peer]