Quintasan (Michał Zając)
- Login: Quintasan
- Registered on: 05/28/2018
- Last sign in: 12/25/2025
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 1 | 2 | 3 |
Activity
04/28/2024
-
12:01 AM Ruby Feature #18915: New error class: NotImplementedYetError or scope change for NotImplementedError
- nithinbekal (Nithin Bekal) wrote in #note-18:
> > What name candidate do you have?
> ...
I like this as well as `AbstractMethodError`
12/20/2023
-
- matz (Yukihiro Matsumoto) wrote in #note-14:
> #note-13 explains my opinion well. What name candidate do you have?
> ...
How about `AbstractMethodError` - the same as Java?
10/13/2023
-
- tenderlovemaking (Aaron Patterson) wrote in #note-8:
> I'm guilty of using `NotImplementedError` for abstract classes. I like the idea of changing the documentation, but on the other hand, since `NotImplementedError` doesn't inherit fr...
07/14/2022
-
- # Abstract
Introduce `NotImplementedYetError` exception that should be used in case when the codepath has not been implemented by the developer for some reason (maybe they're designing an abstract class or are designing some sort of i...
02/07/2022
-
- Would it be possible to backport https://github.com/ruby/ruby/pull/4429 to ruby_3_0?
I did check out the `ruby_3_0` branch, applied the patch. It builds successfully, now I'm running `make check` to verify if it's working.
05/28/2018
-
- Yes, you are right. It was a bug after all but not in the way I originally thought :D.
Hanmac (Hans Mackowiak) wrote:
> you mean the offset right?
> ...
-
- I noticed it today when migrating to Time in my library but DateTime somehow parses incorrect ISO8601 dates. Technically that's a feature but I believe this behaviour is incorrect. Time#iso8601 behaves correctly in this case.
# Steps ...