You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While we now have import Pipe as Pipe2 we don’t have using Pipe as Pipe2 but (#38521) will resolve that; so that it to bring into scope everything exported and rename the module itself.
In that context, it might also make sense to have using Pipe as _ to bring into scope everything exported but not bring the module name itself into scope.
Which would in particular fix the error related to using Pipe as the things it exports do not have name conflicts
The text was updated successfully, but these errors were encountered:
While we now have
import Pipe as Pipe2
we don’t haveusing Pipe as Pipe2
but (#38521) will resolve that; so that it to bring into scope everything exported and rename the module itself.In that context, it might also make sense to have
using Pipe as _
to bring into scope everything exported but not bring the module name itself into scope.Which would in particular fix the error related to
using Pipe
as the things it exports do not have name conflictsThe text was updated successfully, but these errors were encountered: