Thanks for the library, it's working great so far!
For performance, it's sometimes preferable to use ValueTask<T> instead of Task<T> to avoid an allocation if there is no actual asynchronicity involved. Many of my simpler hub methods really do not do anything async, and thus don't benefit from Task<T> on the backend side.
My specific request:
- allow methods in hubs to have a
ValueTask instead of a Task and generate the exact same resulting typescript code
- (optional) allow methods in hubs to just not be async at all, which should be supported by SignalR.
If you want help and a timely release is possible, you can give me code entry points and I can work on this myself.
Thanks for the library, it's working great so far!
For performance, it's sometimes preferable to use
ValueTask<T>instead ofTask<T>to avoid an allocation if there is no actual asynchronicity involved. Many of my simpler hub methods really do not do anything async, and thus don't benefit fromTask<T>on the backend side.My specific request:
ValueTaskinstead of aTaskand generate the exact same resulting typescript codeIf you want help and a timely release is possible, you can give me code entry points and I can work on this myself.