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
There might be no solution here, because name conflicts are in general unavoidable.
We could think about not exporting some of the symbols, but that sounds stupid.
Polyhedra warnings
julia>using LazySets, Polyhedra
# press TAB
julia> WARNING: both Polyhedra and LazySets export"HalfSpace"; uses of it inmodule Main must be qualified
WARNING: both Polyhedra and LazySets export"Interval"; uses of it inmodule Main must be qualified
WARNING: both Polyhedra and LazySets export"Line"; uses of it inmodule Main must be qualified
WARNING: both Polyhedra and LazySets export"dim"; uses of it inmodule Main must be qualified
IntervalArithmetic warnings
Note that the warnings do not appear when only typing using LazySets (because IntervalArithmetic is only loaded internally). So I think we can ignore this.
julia>using LazySets, IntervalArithmetic
# press TAB
julia> WARNING: both LazySets and IntervalArithmetic export"Interval"; uses of it inmodule Main must be qualified
WARNING: both IntervalArithmetic and LazySets export"isdisjoint"; uses of it inmodule Main must be qualified
WARNING: both LazySets and IntervalArithmetic export"radius"; uses of it inmodule Main must be qualified
WARNING: both LazySets and IntervalArithmetic export"∅"; uses of it inmodule Main must be qualified
Plots warning
julia>using LazySets, Plots
# press TAB
julia> WARNING: both Plots and LazySets export"center"; uses of it inmodule Main must be qualified
The text was updated successfully, but these errors were encountered:
I restructured the first post to collect everything we have here.
I think we cannot solve the namespace conflicts, but we should at least make the unit tests robust against known problems.
Polyhedra crash
julia>using Polyhedra; include("runtests.jl")
[...]
WARNING: both LazySets and Polyhedra export"dim"; uses of it inmodule Main must be qualified
LazySets.Ball2: Error During Test
Test threw an exception of type UndefVarError
Expression:dim(b) ==1
UndefVarError: dim not defined
[...]
There might be no solution here, because name conflicts are in general unavoidable.
We could think about not exporting some of the symbols, but that sounds stupid.
Polyhedra
warningsIntervalArithmetic
warningsNote that the warnings do not appear when only typing
using LazySets
(becauseIntervalArithmetic
is only loaded internally). So I think we can ignore this.Plots
warningThe text was updated successfully, but these errors were encountered: