>it is up to the caller whether to start it in a virt thread or a real one. Sorta kinda but not when you're working in a framework that will call your code or

>it is up to the caller whether to start it in a virt thread or a real one. Sorta kinda but not when you're working in a framework that will call your code or working in some library where the abstracted code is non-obvious or uneasy to configure. Maybe its not function coloring, although I wouldn't know what else to call it and I think its quite similar. What would you call the problem?