Hello,
Long story short, I would like to propose to extend the usecase for NotImplementedError to account for cases when the codepath has not been implemented for some reason (similar to Python's NotImplementedError). I did write a proposal on Redmine [1] but I think it wasn't seen yet. If this is not the appropriate place to discuss such things then please let me know where should I post this. I tried browsing archives of ruby-core to see it it would be a better place but the archive link [2] gives a 404 so I'm not really sure if that list is still alive.
[1] https://bugs.ruby-lang.org/issues/18915
[2] http://lists.ruby-lang.org/pipermail/ruby-core/
ruby-core is very much alive, but all lists are being moved to Google
Groups.
-a
···
On Tue, Nov 15, 2022 at 4:15 PM Michał Zając <ruby-lang.org@quintasan.pl> wrote:
Hello,
Long story short, I would like to propose to extend the usecase for
NotImplementedError to account for cases when the codepath has not been
implemented for some reason (similar to Python's NotImplementedError). I
did write a proposal on Redmine [1] but I think it wasn't seen yet. If
this is not the appropriate place to discuss such things then please let
me know where should I post this. I tried browsing archives of ruby-core
to see it it would be a better place but the archive link [2] gives a
404 so I'm not really sure if that list is still alive.
[1] Feature #18915: New error class: NotImplementedYetError or scope change for NotImplementedError - Ruby master - Ruby Issue Tracking System
[2] http://lists.ruby-lang.org/pipermail/ruby-core/
Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
--
Austin Ziegler • halostatue@gmail.com • austin@halostatue.ca
http://www.halostatue.ca/ • http://twitter.com/halostatue
[2] http://lists.ruby-lang.org/pipermail/ruby-core/
I migrate above list to the following site:
https://ml.ruby-lang.org/mailman3/hyperkitty/list/ruby-core@ml.ruby-lang.org/
···
On Wed, Nov 16, 2022 at 1:15 AM Michał Zając <ruby-lang.org@quintasan.pl> wrote:
Hello,
Long story short, I would like to propose to extend the usecase for
NotImplementedError to account for cases when the codepath has not been
implemented for some reason (similar to Python's NotImplementedError). I
did write a proposal on Redmine [1] but I think it wasn't seen yet. If
this is not the appropriate place to discuss such things then please let
me know where should I post this. I tried browsing archives of ruby-core
to see it it would be a better place but the archive link [2] gives a
404 so I'm not really sure if that list is still alive.
[1] Feature #18915: New error class: NotImplementedYetError or scope change for NotImplementedError - Ruby master - Ruby Issue Tracking System
[2] http://lists.ruby-lang.org/pipermail/ruby-core/
Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
______________________________________________
ruby-talk mailing list -- ruby-talk@ml.ruby-lang.org
To unsubscribe send an email to ruby-talk-leave@ml.ruby-lang.org
ruby-talk info -- Info | ruby-talk@ml.ruby-lang.org - ml.ruby-lang.org