Monica S.

`@(AdditionalIncludeDirectory)` should be exposed to references so that a library which uses them can safely be used by dependents, e.g.: - MyApplication (include A) - MySubLibrary (Include B) - MySubSubLibrary...

So as it turns out, as long as you manually specify `ReferenceOutputAssembly="false"`, `OutputItemType="None"` and `CopyToOutputDirectory="PreserveNewest"`, .NET applications can reference native libraries (and probably applications too) just fine. Neat.

Current code has a minimum viable product which allows using GCC-style clang to compile simple binaries, with no dependencies.

Windows support has been added. For consistency, the Microsoft extensions have been disabled for now. We can investigate this later - maybe a `microsoft` property?

At this point the basic framework for unit testing has been written, so what we need now is complete unit tests for things which aren't currently tested or are not...

I was planning on doing something like Discord.Net, which uses an event-based websocket client. On 28 Feb 2017 23:05, "Ashton Tito" wrote: Right now it looks like we are just...

This would likely need a new interface to track these. Initially, something like this: ```cs interface IMetricProvider { void UpdateUdpIngress(int bytesReceived); void UpdateUdpEgress(int bytesSent); // and so on, so forth...

Changes seem fine as-is; all it needs is rebasing onto the latest 1.20.x commit and it should be good to merge.

> I would prefer a simple resource pack-based system, maybe a file with extra splashes, or an extra marker line at the top of splashes.txt to not override previous entries....

> @FiniteReality Are you still looking to work on this PR or is this going to be shelved for now? There's only mild support for it, and no people jumpiung...