Skip to content

Re-export ParseIrOpt to ease custom implementations of FromValue#384

Open
LeoniePhiline wants to merge 1 commit intoblackbeam:masterfrom
LeoniePhiline:feat/re-export-parse-ir-opt
Open

Re-export ParseIrOpt to ease custom implementations of FromValue#384
LeoniePhiline wants to merge 1 commit intoblackbeam:masterfrom
LeoniePhiline:feat/re-export-parse-ir-opt

Conversation

@LeoniePhiline
Copy link

Trying to implement FromValue for a custom type, based on ParseIrOpt<bool>, I noticed that ParseIrOpt is not re-exported.

Needing to add mysql_common as direct dependency causes overhead, as compatible version updates must be coordinated. (For example, the current mysql_async 0.36 requires mysql_common 0.35, while a newer mysql_common 0.36 would be available.)

Re-exporting ParseIrOpt allows users of mysql_async to implement FromValue for custom types without needing to manage this added dependency.

@LeoniePhiline
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant