638
edits
GC API: Difference between revisions
Jump to navigation
Jump to search
→Decisions: update after today's meeting
(→Allocation: update after today's irc meeting) |
(→Decisions: update after today's meeting) |
||
| Line 18: | Line 18: | ||
The purpose of this API is to support switching to a different GC implementation ''at compile time'', not at run time. (Each implementation will have its own header file, with its own inline functions or function-like macros. Maybe we'll produce a GC API header file that has no inline anything, just showing the signatures the implementation must provide, for reference.) | The purpose of this API is to support switching to a different GC implementation ''at compile time'', not at run time. (Each implementation will have its own header file, with its own inline functions or function-like macros. Maybe we'll produce a GC API header file that has no inline anything, just showing the signatures the implementation must provide, for reference.) | ||
We will not support any kind of reference counting until we hit the use case that compels us to implement it. (Jason Evans in particular wants to try other optimizations first.) | |||
'''Open issue:''' API style. (C or C++? Use templates? What naming conventions? I think it's too early to ask these questions. So please consider all the function signatures below to be pseudocode.) | '''Open issue:''' API style. (C or C++? Use templates? What naming conventions? I think it's too early to ask these questions. So please consider all the function signatures below to be pseudocode.) | ||