Christoph Läubrich

I think the most critical part actual is: **Can we (reliable) implement it that way**? If that do not work, is prone to bugs, deadlocks or other behavioral changes (e.g....

> Maybe we could try to make it synchronous in the OS specific SWT fragments where we know for sure the native code is asyncronous right now (like GTK), as...

> For the methods such as Clipboard.getContents() there is no option, it must be synchronous (or we redesign SWT API). I think it would be good to at least offer...

There is also `Path.of(...)` (what seems quite common for many interface based types like List/Map/... as well).

> But should we really add recommendation to handle Exports and imports like this in the spec.? As an example we have similar for Require Bundle here: https://docs.osgi.org/specification/osgi.core/8.0.0/framework.module.html#i3198951

This one here gave another (interesting) example that is not really covered by the spec: - https://github.com/bndtools/bnd/issues/6431#issuecomment-2609087792 From the spec text it is not clear if a substitution packages is...

This section does not talk about optional at all: [3.6.6 Importing Exported Packages ](https://docs.osgi.org/specification/osgi.core/8.0.0/framework.module.html#i3238802) so currently the information is hidden in another chapter about resolving here [3.8.1 Importing and Exporting...

Yes something like this, I don't know where it would actually be useful at all to use optional with substitution it must be a completely crazy use case: 1. Your...

> This is already pretty broken! I hoped so but the spec specifically allows it here [3.8.1 Importing and Exporting the Same Package](https://docs.osgi.org/specification/osgi.core/8.0.0/framework.module.html#framework.module-import.export.same.package) > Unresolved - **There is no matching...

I would even argue we should change the default for `@Export` annotation to *not* reeeport, the default is "let the tooling decide" what is both vague and dangerous as different...