Access inner value via RefinedTypeOps extension

[antonkw]

No description provided.

[Iltotore]

Since value is already used for apply, either etc... I think it would be a better name than raw. Also I think it should return a A :| C to not loose the refinement.

Note that A :| C is already a subtype of A so for an extension like inline def value: A :| C = thisValue.asInstanceOf[A :| C] the following code compiles:

//Assuming `Temperature` is an (opaque) alias for `Double :| Positive`
val temperature: Temperature = Temperature(5)

//Both work
val withRefinement: Double :| Positive = temperature.value
val raw: Double = temperature.value

[antonkw]

I was inclined to use value but then recalled that value is something that is used as both:

• a conventional name for lightweight newtypes-like wrappers
• accessing underlying data (one level down) in e.x. refined library

Hence, to access the underlying IronType (what you've suggested), value is the right name. I was thinking about the equivalent of value.value but it is just not necessary (see below).

Also I think it should return a A :| C to not loose the refinement.

Completely agree. I missed that subtyping makes temperatureX.value + temperatureY.value fully legitimate.

Updated PR to have value:

extension (wrapper: T)
    inline def value: IronType[A, C] = wrapper.asInstanceOf[IronType[A, C]]

Now there is an experience of "unpacking" opaque types (without affecting any previously stated obligations):

val t1 = Temperature(100)
val t2 = Temperature(100)

val result = t1.value + t2.value