upgrade to Zenoh V0.6.0-dev.0

[sanri]

No description provided.

[JEnoch]

Hi @sanri,

Thanks for your interest in Zenoh and for your efforts upgrading this C# API!
By lack of time and resources we unfortunatly had to pause the developments of this API, prioritizing the most used APIs so far: Rust, Python and C. But we'll be happy to have contributors helping us to develop a Zenoh C# API that comply with the semantic and style of the other Zenoh APIs.

Just to let you know, we're about to release a new version of Zenoh that includes some significative changes in all its APIs (zenoh-c included).
You can see the work in progress in all the api-changes branches for our repos. And those branches will be merged in to the main branches of their respective repos in the coming days. Then, we'll release all as v0.6.0-beta.1.

We think the best is for the C# API update to rely on this new zenoh-c v0.6.0-beta.1. Also, we would like to expose in C# a similar semantic than the other APIs (i.e. type and function names, builder patterns...), but at the same time relying on the common C# idoms (e.g. implement IDisposable).

Would you like to help us achieving this goal ?
If so, I encourage you to join us on our Discord where you could discuss this with @p-avital who is the lead for all Zenoh APIs.

[p-avital]

Hi,

To be more precise, what we would be looking for would be:

• Implement IDisposable for all types, with a finalizer ensuring that dispose is called during a GC pass if the user failed to dispose of things properly.
• Use default values for extra parameters, much like we've done in the upcoming python API (also on branch api-changes), and if you know of a way to restrict their usage to named usage, it would be preferable.
• For a lot of things, we prefer accepting many different types as input. I think the most well suited way of doing that in C# would be a combination of generics (relying on interfaces similar to the traits required in the Rust version) and overloads (for standard types, which we unfortunately cannot implement interfaces for externally).

I haven't done C# in a long time, so I'm experimenting with it at the moment to figure out how we can best leverage it to make an API for Zenoh as comfortable as possible.

If you'd rather keep your bindings as reexports of the C bindings, I completely understand: I'm potentially asking for a lot of work. If you don't feel like doing it, we'll push it back on our todo-list and try to get to it eventually :)

[sanri]

Hi, I haven't done C# in a long time too (^_^) . We are using Zenoh for our ongoing project, I tried to provide Zenoh C# bindings to the C# engineers on my team. I'll keep track of zenoh-c v0.6.0-beta.1 branch, and try to achieve those goals.

Also, we would like to expose in C# a similar semantic than the other APIs (i.e. type and function names, builder patterns...), but at the same time relying on the common C# idoms (e.g. implement IDisposable).

Please forgive me for my poor English.