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
When building Mux, the following warning is displayed:
WARNING: using HTTP.stack in module Mux conflicts with an existing identifier.
This can be fixed easily by changing the using HTTP statements (in 2 places) to using HTTP: HTTP
This looks a bit odd and I could not find this particular syntax in the documentation anywhere, but it works. What it does is to just make the module HTTP reachable within Mux and its included files, without actually bringing all the names exported by HTTP into the Mux scope. Among the exports is stack. Mux has its own declaration of stack, which is causing the conflict.
In Mux all references to HTTP internals are done with dot-syntax so it is not necessary to bring into Mux any of the HTTP exports. Only the namespace of the module HTTP is needed and this is what the suggested code achieves.
I can provide the necessary PR if the above change sounds acceptable
Kobus
The text was updated successfully, but these errors were encountered:
By "building Mux", I assume you mean loading Mux (Mux doesn't have a build step)?
But yes, that sounds fine to me! import HTTP will likely be what we should do to be idiomatic (it only brings in the module, but doesn't bring exports into scope).
When building Mux, the following warning is displayed:
This can be fixed easily by changing the
using HTTP
statements (in 2 places) tousing HTTP: HTTP
This looks a bit odd and I could not find this particular syntax in the documentation anywhere, but it works. What it does is to just make the module HTTP reachable within Mux and its included files, without actually bringing all the names exported by HTTP into the Mux scope. Among the exports is
stack
. Mux has its own declaration of stack, which is causing the conflict.In Mux all references to HTTP internals are done with dot-syntax so it is not necessary to bring into Mux any of the HTTP exports. Only the namespace of the module HTTP is needed and this is what the suggested code achieves.
I can provide the necessary PR if the above change sounds acceptable
Kobus
The text was updated successfully, but these errors were encountered: