If any reader knows enough about what this paper covers to assess the potential (ir)relevance of this to Rakudo please comment.
arxiv.org/abs/2411.1654450
raiph
u/raiph
arxiv.org
Float Self-Tagging: a new approach to object tagging that can attach type information to 64-bit objects while retaining the ability to use all of their 64 bits for data
arxiv.org/abs/2411.1654410
We have "Bisectable – find out when regression happened" -- but what about finding out where it happened?
Quoting the recent blog post Bisecting Program Locations:
10
https://yakshavingcream.blogspot.com/ looks to me like it's been hacked by a bot.
Which would suggest we're likely to lose the pages the blog contains about the GSoC work (eg https://yakshavingcream.blogspot.com/2019/08/summer-in-review.html ).
Am I wrong?
If I'm right, does anyone know if that content is already preserved somewhere? And if not, what's a sensible way to determine and preserve the content that matters? I'm guessing the latter would be Liz's Collect, Conserve, R-something project, right?
34
109
Before I get to discussing an infix where, let me introduce a motivating example.
Consider this code, a condensed example of the problem raised in the SO "Does pattern match in Raku have guard clause?":
$_ = 99;
when Int and 42 { .say } # 99
Imo this will forever be surprising to newbies, and we would be well advised to address it.
One thing I hope for is that one day there will be a compile time error whenever logical conjunctions such as &&, and, andthen, or or, ||, or orelse are used, and the compiler knows at compile time that the LHS will make either the LHS or RH
32
20
20
The ACM SIGPLAN Conference on Programming Language Design and Implementation (PLDI) 2023: free and open to virtual attendees
mastodon.acm.org/@pldi/11055069419121571181
90
I am thinking it might be good to start posting regular polls on various topics in this sub. But maybe not?
Anyhoo, I thought I'd kick things off with a poll about polling. I've deliberately heavily biased this poll's options in an anti-polling direction because A) I want to make it clear I'm aware they tend to be fairly unhelpful noise, and B) I actually want folk to be reticent to even vote let alone comment. That said, I'm quite obviously not 100% against them either! If you really think systematic polling might be a worthwhile thing, please engage with this one by at least voting on an option.
I'm ready to say more about the polling I'm thinking we might do, but I'll first wait to see
710
SYNOPSIS
A new declarator:
foo = 42
Before you go with your immediate gut instinct and start formulating a reply, please take a moment to do something else to clear those initial emotions, and read the rest of this proposal. Thanks!
DETAILS
Currently a program with just:
foo = 42
yields:
SORRY! Error while compiling
Preceding context expects a term, but found infix = instead.
Did you make a mistake in Pod syntax?
What if instead it did an equivalent of this:
constant foo = 42
?
----
In existing Raku code, if foo is already declared in the lexical scope you'll get the same error unless foo has been declared as a term (sub term:<foo>).
I
531