Re: [whatwg/webidl] How are name conflicts specified? (Issue #1411)

Sorry, to be a little more specific, the conflict is referring to the type and the operation name having the same name. In my specific case, we use interop to [provide interfaces](https://github.com/dart-lang/web) for browser APIs in Dart. Dart disallows you from declaring a member with the same name as its return type e.g.

```dart
class A {}
A A() {} // error
```

This issue doesn't occur with the `URL` case presumably since the use of the type `URL` isn't in the same declaration as the declaration of the member `URL`. C++ seems to be okay with similar code, although it does warn you that you're changing the meaning of `A`.

Regardless, it seems like this is well-defined and there's precedent, so it's a matter of me handling this specially to account for language differences. The other name conflict I've come across is operations having the same name as static operations (which also is an issue in Dart), which we already handle specially. I'll mark this as closed.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/issues/1411#issuecomment-2177063483
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/issues/1411/2177063483@github.com>