Fixed
Status Update
Comments
cc...@google.com <cc...@google.com>
ap...@google.com <ap...@google.com> #2
Can you rise priority please?
It's a real stopper to use in not helloworld apps.
It must be joke, define it as "An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system."
Why use compose in production, if this base things resolved for years?
It's a real stopper to use in not helloworld apps.
It must be joke, define it as "An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system."
Why use compose in production, if this base things resolved for years?
Description
From internal report, seeing errors like the following:
map is ambiguous with lambda syntax, due to having the same lambda signature for both variants.
Note - can't make it an extension in this case, since it's open (for legacy reasons).