@ASCII-only can you figure out memory management

we need GC

or ref counting. but that is v expensive

GC is better for this moment

@ASCII-only ok so I am plan on have 4 type of value:

value (bitset), reference<T> (T*), complex value (struct), multi value (tuple)

for reference<T> I was thinking we could just have like a value.isReference prop

@Downgoat huhwhat?

so when you have like value

its stored in memory

but LLVM has special types (e.g. int)

which can have special operation run on them

and then they are other type like array

which contain multiple of these things e.g. int

umwhat

what exactly does reference have to do with this

ok so lets say you have object right

object is passed by reference

let a = Goat()

to manage memory we are use ref counting right?

@Downgoat :|

is slow

researcher.watson.ibm.com/researcher/files/us-groved/…

you want to do GC instead?

yeah

maybe ref counting for now? idk

uh gc is slower

because it has to stop whole program

that one doesn't

also worse on memory

that is pauseless

because we have to store all reference

isn't it same for ref counting

no

but also gc/mm should be only used when needed

e.g. no gc for like factorial and hello world

ref count is like let a = Goat() become a = Reference(Goat()); a.increment() instead of like a = Goat() directly

@ASCII-only pls provide elaboration of this GC method

specifically how to detect when should be use and not be use

and when it should be called

ok apparently this is better azul.com/resources/azul-technology/azul-c4-garbage-collector

@Downgoat when all object dying time can be predicted then don't use gc at all

@ASCII-only 0/10 cost money to see whitepaper

@ASCII-only how to predict object dying time

@Downgoat nvm is need special hardware anyway

@Downgoat last time object is used

if object not pass out of function and all calls with object have finished using

@ASCII-only how do you identify when the last time an object is used? How do you know which path program execution will take

@Downgoat doesn't matter, free memory last time it is used on specific path

if it's freed on both then free after the calls on both

@ASCII-only can u provide sample implement staging.vihan.org/LLIR/docs