kylemacey (Kyle Macey)
- Login: kylemacey
- Email: shout@kylemacey.com
- Registered on: 06/18/2019
- Last sign in: 06/18/2019
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 1 | 0 | 1 |
Activity
06/20/2019
-
07:18 PM Ruby Feature #15936: on_error in lieu of rescue, raise
- duerst (Martin Dürst) wrote:
> kylemacey (Kyle Macey) wrote:
> ...
Very true! I can certainly do that, I just thought this might have the added benefit of writing more explicit and intentional code, and would eliminate the need to re-r... -
07:17 PM Ruby Feature #15936: on_error in lieu of rescue, raise
- jeremyevans0 (Jeremy Evans) wrote:
> kylemacey (Kyle Macey) wrote:
> ...
`ensure` fires even if there is no exception. This keyword would only fire when there is an exception. In your example, `job.fail!` would always be called.
Edi...
06/19/2019
-
01:56 AM Ruby Feature #15936: on_error in lieu of rescue, raise
- shevegen (Robert A. Heiler) wrote:
> Hmmm.
> ...
Yeah, this is a proposal to extend the available keywords in ruby core. So ideally, there would be release notes and documentation that would help guide people to this new feature.
> ...
06/18/2019
-
06:28 PM Ruby Feature #15936 (Open): on_error in lieu of rescue, raise
- A common bad pattern in ruby is to rescue any exception and accidentally clobber the exception.
```
begin
some_method
rescue StandardError
#
end
```
Most linters will complain if you write rescues like the code above. H...