Setting aside whether or not the existing functionality is intuitive or not, this isn't actually a proposal. You aren't suggesting an alternative.
On Thursday, September 21, 2017 at 10:17:12 AM UTC-4, Krzysztof Wende wrote: > > Right now when we import a module A > > defmodule CurrentA do > def public1, do: 1 > def public2, do: 2 > def public3, do: 3 > end > > > defmodule CurrentA do > import CurrentA, only: [public1: 0] > import CurrentA > > def test, do: public2() # No problem whatsoever > end > > But whenever we add `except` to it > > defmodule CurrentA do > def public1, do: 1 > def public2, do: 2 > def public3, do: 3 > end > > > defmodule CurrentA do > import CurrentA, only: [public1: 0] > import CurrentA, except: [public3: 0] > > def test, do: public2() # undefined function public2/0 > end > > We get an error of inexistent function. For me it feels super > counter-intuitive. > > Thoughts? > Cheers, > Krzysztof > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/7f1e33c3-21d4-4c0f-b176-bdcc1fe35f81%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
