Stop using smartmatch ~~ #15

Closed
opened 2024-08-19 08:07:28 +00:00 by nu · 3 comments
Owner

I don't think it does what I thought it did back when I started using it, so it'd be better to just... Not.

I don't think it does what I thought it did back when I started using it, so it'd be better to just... Not.
nu added this to the CharmBoard v1.0 milestone 2024-08-19 08:07:28 +00:00
nu added the
improvement
label 2024-08-19 08:07:28 +00:00
Author
Owner

For, i.e. the database type checker, it might be better to force lowercase the config value before comparing it, so if someone types SQLite in the config instead of sqlite then it doesn't die unnecessarily. I believe this is what I intended when deciding to use smartmatch here.

For, i.e. the database type checker, it might be better to force lowercase the config value before comparing it, so if someone types `SQLite` in the config instead of `sqlite` then it doesn't die unnecessarily. I believe this is what I intended when deciding to use smartmatch here.
Author
Owner

For, i.e. the database type checker, it might be better to force lowercase the config value before comparing it, so if someone types SQLite in the config instead of sqlite then it doesn't die unnecessarily. I believe this is what I intended when deciding to use smartmatch here.

For, i.e. the database type checker, it might be better to force lowercase the config value before comparing it, so if someone types `SQLite` in the config instead of `sqlite` then it doesn't die unnecessarily. I believe this is what I intended when deciding to use smartmatch here.
Author
Owner

Yeah... That's literally the only place I was using smartmatch. Now to go through and change each use experimental qw(try smartmatch); line to just use experimental qw(try); in every. single. PM file.

Yeah... That's literally the only place I was using smartmatch. Now to go through and change each `use experimental qw(try smartmatch);` line to just `use experimental qw(try);` in every. single. PM file.
nu closed this issue 2024-08-19 08:14:28 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: nu/CharmBoard#15
No description provided.