dumblob
dumblob
> I would recommend against even a `#pragma message` , as it could get quite annoying for builds that are not affected by the deprecated code. What do you mean?...
@RobLoach perhaps the function would be a macro... `@deprecated` is fine - but it's only for documentation (and not for build), so not enough on its own.
Generally this looks like a promising approach to me. >It requires the user to provide image-size upon image creation, no exceptions. This though is a bit too strict in my...
> Huh... Now that you mention it, maybe that is too strict. So keep the old commands, always defaulting to NK_IMAGE_STRETCH and create a set of new ones, where you...
Nice, thanks. Do you still plan to work on the last TODO items in the initial post above or shall we make our hands dirty with a full-scale review already?
If it's how @exchg sketched out, then we can't do much about this. Shall we contact clang team to reconsider how they perform the sanitization?
Added rawdraw to the list :wink:.
It's true it doesn't look consistent even though it's superficial from the implementation point of view.
This is clearly a type error - last line says it explicitly. `tup2` was apparently already initialized (last line says that the original type was `tuple`, i.e. something like `var...
Recently I've attended talks about _Go_ lang and _Ceylon_ on [DevConf 2015](http://devconf.cz/) and the most interesting question from the audience (asked in both talks by different person) was about signature...