cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake https://pypy.org | IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end and https://libera.irclog.whitequark.org/pypy | the pypy angle is to shrug and copy the implementation of CPython as closely as possible, and staying out of design decisions
<korvo> Hey, quick question from #esolangs where we are talking about fat pointers and interpreter implementation. Are RPython classes compiled to fat pointers or does each object have a pointer to its class/vtable?
* korvo okay with being embarrassed to not know this
itamarst has quit [Quit: Connection closed for inactivity]
auk has quit [Quit: Leaving]
Dejan has joined #pypy
itamarst has joined #pypy
<cfbolz> korvo: rpython instances are heap allocated, and they have a thin pointer to their class/vtable as part of the header word
<korvo> cfbolz: Got it, thanks.
Dejan has quit [Remote host closed the connection]
Dejan has joined #pypy
Dejan has quit [Remote host closed the connection]