Paul Connelly

> our function returns an object that doesn't have a public type How is anybody supposed to use your API if they can't know anything about its return type? Can...

> I like this approach best. I don't. I'd prefer if people can't accidentally discover that we have broken their code. I'd also prefer that types used in public function...

@aruniverse @calebmshafer @wgoehrig @ben-polinsky please review proposed strategy illustrated in #6783.

@aruniverse @calebmshafer @wgoehrig @ben-polinsky please provide feedback on the proposed strategy illustrated in #6783.

> I'm not sure we can rely on it. Given our goal is to never break compilation of apps that use public APIs when they upgrade to a minor or...

@aruniverse and @wgoehrig pointed out a potential pitfall with using unique symbols. If somebody's dependencies cause them to pull in multiple versions of, say, core-bentley, then core-bentley will contain two...

A handful of `internal` methods in core-backend are invoked by native code, so cannot be changed to symbols. Many of these are `private` and I believe the rest can be...

In 4.2.x and earlier did the terrain get greyed out like the non-emphasized elements?

Thanks. So, not a regression in the emphasize behavior, but a change in the widget behavior? If you toggle "Locateable" OFF in the widget, you should be able to select...

I'm not sure what tool you are using in your recording. See if your tool sets [allowNonLocatable](https://www.itwinjs.org/reference/core-frontend/locatingelements/locateoptions/#allownonlocatable) to false. See if the normal selection tool allows you to locate the...