You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The RefineM macro can currently be invoked via the refineM functions (e.g. refineMV[Positive](1)) or via an implicit conversion which needs to be imported with import auto._ (it then can be invoked with 1: (Int Refined Positive)). It would be nice if users of refined could write their own aliases for RefineM with fixed types and without importing an implicit conversion. See https://github.com/quasar-analytics/quasar/pull/1025 for more context.
We can support this with a variation of the RefineMPartiallyApplied class:
`refineMF` is a variation of `refineM` but which requires that the base
type is specified before `apply` can be called. This allows to create
aliases like `val Natural = RefType[Refined].refineMF[Long, NonNegative]`
which only can be called with `Long` arguments.
closes#107
`refineMF` is a variation of `refineM` but which requires that the base
type is specified before `apply` can be called. This allows to create
aliases like `val Natural = RefType[Refined].refineMF[Long, NonNegative]`
which only can be called with `Long` arguments.
closes#107
The
RefineM
macro can currently be invoked via therefineM
functions (e.g.refineMV[Positive](1)
) or via an implicit conversion which needs to be imported withimport auto._
(it then can be invoked with1: (Int Refined Positive)
). It would be nice if users of refined could write their own aliases forRefineM
with fixed types and without importing an implicit conversion. See https://github.com/quasar-analytics/quasar/pull/1025 for more context.We can support this with a variation of the
RefineMPartiallyApplied
class:/cc @jedesah
The text was updated successfully, but these errors were encountered: