track the "owner" heap object in the ref write barrier
See the papers for reference counting with heap sliding views for details:
This commit is contained in:
parent
c67520a7c5
commit
e9e22ccb2a
4 changed files with 98 additions and 8 deletions
|
|
@ -233,7 +233,7 @@ proc binaryStrSearch*(x: openarray[string], y: string): int =
|
|||
result = - 1
|
||||
|
||||
# Can we keep this? I'm using it all the time
|
||||
template nimdbg*: expr = c.filename.endsWith"hallo.nim"
|
||||
template cnimdbg*: expr = p.module.filename.endsWith"hallo.nim"
|
||||
template enimdbg*: expr = c.module.name.s == "hallo"
|
||||
template pnimdbg*: expr = p.lex.fileIdx.ToFilename.endsWith"hallo.nim"
|
||||
template nimdbg*: expr = c.module.fileIdx == gProjectMainIdx
|
||||
template cnimdbg*: expr = p.module.module.fileIdx == gProjectMainIdx
|
||||
template pnimdbg*: expr = p.lex.fileIdx == gProjectMainIdx
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue