dumblob

`nk_xlib_init()` exists to do some X11 stuff **and** allocate and pre-fill the Nuklear context for you. If you ignore the newly created context, you're probably out of luck as it...

You're comparing backends like apples and oranges, same goes for other things. I will not comment on that as it leads nowhere. > it seems like one'd need to know...

No, it's not a wrapper as the full signature is `NK_INTERN void nk_xsurf_clear(XSurface *surf, unsigned long color)` and `NK_INTERN` means the function shall be used only internally (i.e. it's an...

There is a good real-time memory allocator available on http://www.gii.upv.es/tlsf/ (see a brief [comparison to some other allocators](http://www.gii.upv.es/tlsf/alloc/others )). It's GPL licensed, but the research papers are all available on...

This is in line with my observations. I just can't take the ownership of this effort due to lack of time. I wonder what others think.

Maybe, it mangles also something more: ``` ruby load os routine r() { os.sleep(1) } routine main() { fut = r()!! defer { fut.value() } return 0 } ``` returns...

> besides, they offer no compile-time checks. Do you have any specific examples, where compile-time checks make sense? I can hardly imagine I would leverage it, because all my work...

> Unfortunately, it's not possible to bind the type of what `decompose()` returns to `text` parameter of `compose()`. That can't be solved without something akin to Rust's associated types, which...

>Unfortunately, it's not possible to bind the type of what decompose() returns to text parameter of compose(). That can't be solved without something akin to Rust's associated types, which would...

One idea would be to make the interface also a streaming interface (i.e. handle an infinite input stream). Code sections might come handy...