Daniel Weber

@SimonCropp Do you think this is of any use to the project, or rather outside its scope?

Thanks for having a look into it. I'll try to identify the directives and give it a try.

It seems the [line you references](https://github.com/BepInEx/HarmonyX/blob/55fb4e2eea496531d9156c8c3a0b3d2b43b38b00/Harmony/Internal/PatchTools.cs#L40-L42) is the only one that mentions .NET6 but given the only core-target of the main library is netstandard, the NET6 directive doesn't do that...

Just wildly guessing here: If it's got something to do with tiered compilation, there was a [reimplementation in .NET 7 Preview 3](https://github.com/dotnet/runtime/pull/65738). [Complete changelog of preview 3.](https://github.com/dotnet/core/issues/7108)

Thanks a lot @ghorsington!

Closing here, see https://github.com/MonoMod/MonoMod/issues/94 for further tracking.

There's no dots in ^([0-9]*) but 1.2.3 got dots.

Having some notion of a respone object could be nice, however, I wouldn't like to force clients to having to project from Response to TResult everywhere in their code. Maybe...

I think a possible WithMeta method should leave the query domain (`I...Query`) and change to an `IAsyncEnumerable`. On an IAsyncEnumerable there's all the known extensions (ToArrayAsync etc.).

What's especially misleading is that, while `outerCommand --help` would print ``` outerCommand innerCommand ``` suggesting that `arg` is required even when invoking `innerCommand`, it's not how the library behaves. @jonsequitur...