02:58 ilbot3 joined 03:17 unicodable6 joined, benchable6 joined 03:50 Geth joined 03:51 Geth joined 03:53 p6lert joined
[Coke] mst: is there anything you can do to prevent that kind of spam? 04:04
05:39 Zoffix joined 07:30 geekosaur joined 07:32 piojo joined
piojo so MVMObject is a type object, and there should be one MVMObject instance per type, right? 07:38
for example, Array[Int] corresponds to one MVMObject? Or is it just Array that has a MVMObject? 07:40
FYI, I'm looking into this: rt.perl.org/Public/Bug/Display.html?id=128287 07:41
And I found type_check_store() does the bad check, but the logic itself is probably okay. The runtime data is probably the problem--duplicate types in memory.
geekosaur pretty sure every object has an MVMObject somewhere under it, and types are objects (of type Class iirc) 07:43
piojo geekosaur: oh, that sounds like turtles all the way down. very self-supporting, conceptually 07:46
geekosaur most pure object systems (e.g. smalltalk) also work that way 07:47
piojo Could you help me understand the meaning of this type check? github.com/rakudo/rakudo/blob/mast...iner.c#L97 08:12
I think "cont" is one type, and "tc" somehow contains a reference to the other type 08:13
no, that can't be right. it must be rcd and obj, with tc holding extra info 08:14
geekosaur proibably not; I don't know much about the internal details, sorry 08:17
piojo thanks anyway, I understand it now. The problem must be at a higher level
geekosaur and atsome point probably only jnthn can help you
piojo my thought is that either: 08:18
1) the decision to use type caches is incorrect,
2) the type caches are incorrect, or
3) there are duplicate type objects so of course they don't exist in each other's type caches
.ask jnthn Could you please take a look at this bug? I've debugged it some but it's really out of my league: rt.perl.org/Ticket/Display.html?id...50f25eb6ab 09:21
yoleaux piojo: I'll pass your message to jnthn.
09:21 domidumont joined 09:27 domidumont joined
piojo .tell jnthn I added comments that I hope will be useful, but the next step requires understanding how how MVMObjects are created (or looked up) as modules are parsed after (not during) compilation. 09:28
yoleaux piojo: I'll pass your message to jnthn.
09:29 FROGGS joined 11:15 piojo_ joined
Zoffix Announcing P6lert: Perl 6 Alerts Directly From Core Developers: rakudo.party/post/Announcing-P6ler...Developers 11:24
11:58 Zoffix left 15:53 statisfiable6 joined 16:05 nativecallable6 joined, quotable6 joined, releasable6 joined, committable6 joined 16:56 FROGGS joined 17:26 piojo_ joined 19:38 bisectable6 joined, bloatable6 joined, squashable6 joined, coverable6 joined, greppable6 joined 20:58 evalable6 joined, reportable6 joined 21:22 geospeck joined 21:30 AlexDaniel joined 21:42 Ven`` joined