>doesn't have C's repeated overhead of pulling in include files.
Sorry, typo - I meant to say "C++'s repeated ..."
C may have it too, don't remember if so or not right now.
The video mentioned in my above comment has some details on why this is such an issue in C++ - from the source, i.e. Stroustrup, the creator of C++. There's a bit of humor around that fragment of the talk - it is somewhere near the end, IIRC.
D meets some of your criteria too, at least somewhat small fast, native apps. Build speed is decent (or more) too, and it is designed for that - doesn't have C's repeated overhead of pulling in include files. [1] Haven't tried the GUI toolkits for D though (yet). There are some, like DLangUI, GtkD, etc. Not sure if there are any GUI builders like Delphi, Lazarus, VB, Xojo, etc. have. Also, I think I read that D's language design allows D compilers to be the single-pass kind.
[1] I think this is the video I had blogged about a while ago, in which Bjarne Stroustrup talks about the details of that include files issue:
Video: C++, Rust, D and Go: Panel at LangNext '14
https://jugad2.blogspot.com/2016/08/video-c-rust-d-and-go-pa...
Edited for wording about D compilers.