Issue with generic Unit of Measures / match











up vote
1
down vote

favorite












I have read quite a few ressources on Unit of Measures (including the good Microsoft Doc and f# for fun and profit) but I still cannot make my code work.



[<Measure>] type USD
[<Measure>] type JPY
[<Measure>] type EUR

type FxUnit<[<Measure>] 'u,[<Measure>] 'v> = {UnitRate : float<'u/'v>}

let getFx1 u =
match u with
| "USD" -> {UnitRate = 1.0<USD/USD>}
| "EUR" -> {UnitRate = 1.0<USD/EUR>}


This way I get an error under:



1.0<USD/EUR>


I have tried thse:



let getFx1  u : (float<'u>) =
let getFx1 u : (float<'u/'v>) =


without much success. It seems that with a match, I can't return some type FxUnit with different UoM.



Any idea how I could fix this?



thanks.










share|improve this question


















  • 1




    This seems to be consistent with the general usage of type parameters; for example, if you have a function returning a 'a list, you cannot return a float list from one branch and a int list from another branch. It might work if you declare your function getFx1 as inline (as the compiler will then use statically resolved type parameters).
    – dumetrulo
    Nov 20 at 12:50








  • 1




    The thing with Unit of Measures is that they are a feature to let the compiler verify that your arithmetic logic is sound so you do not end up for instance adding Yens + Euros. For that to work you need to have values with specific UoMs. If they were to be generic then the compiler cannot help you anymore and they lose their usefulness. So, there are very few things you can do with generic UoMs.
    – AMieres
    Nov 20 at 14:08















up vote
1
down vote

favorite












I have read quite a few ressources on Unit of Measures (including the good Microsoft Doc and f# for fun and profit) but I still cannot make my code work.



[<Measure>] type USD
[<Measure>] type JPY
[<Measure>] type EUR

type FxUnit<[<Measure>] 'u,[<Measure>] 'v> = {UnitRate : float<'u/'v>}

let getFx1 u =
match u with
| "USD" -> {UnitRate = 1.0<USD/USD>}
| "EUR" -> {UnitRate = 1.0<USD/EUR>}


This way I get an error under:



1.0<USD/EUR>


I have tried thse:



let getFx1  u : (float<'u>) =
let getFx1 u : (float<'u/'v>) =


without much success. It seems that with a match, I can't return some type FxUnit with different UoM.



Any idea how I could fix this?



thanks.










share|improve this question


















  • 1




    This seems to be consistent with the general usage of type parameters; for example, if you have a function returning a 'a list, you cannot return a float list from one branch and a int list from another branch. It might work if you declare your function getFx1 as inline (as the compiler will then use statically resolved type parameters).
    – dumetrulo
    Nov 20 at 12:50








  • 1




    The thing with Unit of Measures is that they are a feature to let the compiler verify that your arithmetic logic is sound so you do not end up for instance adding Yens + Euros. For that to work you need to have values with specific UoMs. If they were to be generic then the compiler cannot help you anymore and they lose their usefulness. So, there are very few things you can do with generic UoMs.
    – AMieres
    Nov 20 at 14:08













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have read quite a few ressources on Unit of Measures (including the good Microsoft Doc and f# for fun and profit) but I still cannot make my code work.



[<Measure>] type USD
[<Measure>] type JPY
[<Measure>] type EUR

type FxUnit<[<Measure>] 'u,[<Measure>] 'v> = {UnitRate : float<'u/'v>}

let getFx1 u =
match u with
| "USD" -> {UnitRate = 1.0<USD/USD>}
| "EUR" -> {UnitRate = 1.0<USD/EUR>}


This way I get an error under:



1.0<USD/EUR>


I have tried thse:



let getFx1  u : (float<'u>) =
let getFx1 u : (float<'u/'v>) =


without much success. It seems that with a match, I can't return some type FxUnit with different UoM.



Any idea how I could fix this?



thanks.










share|improve this question













I have read quite a few ressources on Unit of Measures (including the good Microsoft Doc and f# for fun and profit) but I still cannot make my code work.



[<Measure>] type USD
[<Measure>] type JPY
[<Measure>] type EUR

type FxUnit<[<Measure>] 'u,[<Measure>] 'v> = {UnitRate : float<'u/'v>}

let getFx1 u =
match u with
| "USD" -> {UnitRate = 1.0<USD/USD>}
| "EUR" -> {UnitRate = 1.0<USD/EUR>}


This way I get an error under:



1.0<USD/EUR>


I have tried thse:



let getFx1  u : (float<'u>) =
let getFx1 u : (float<'u/'v>) =


without much success. It seems that with a match, I can't return some type FxUnit with different UoM.



Any idea how I could fix this?



thanks.







f#






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 20 at 11:05









Jeff_hk

736




736








  • 1




    This seems to be consistent with the general usage of type parameters; for example, if you have a function returning a 'a list, you cannot return a float list from one branch and a int list from another branch. It might work if you declare your function getFx1 as inline (as the compiler will then use statically resolved type parameters).
    – dumetrulo
    Nov 20 at 12:50








  • 1




    The thing with Unit of Measures is that they are a feature to let the compiler verify that your arithmetic logic is sound so you do not end up for instance adding Yens + Euros. For that to work you need to have values with specific UoMs. If they were to be generic then the compiler cannot help you anymore and they lose their usefulness. So, there are very few things you can do with generic UoMs.
    – AMieres
    Nov 20 at 14:08














  • 1




    This seems to be consistent with the general usage of type parameters; for example, if you have a function returning a 'a list, you cannot return a float list from one branch and a int list from another branch. It might work if you declare your function getFx1 as inline (as the compiler will then use statically resolved type parameters).
    – dumetrulo
    Nov 20 at 12:50








  • 1




    The thing with Unit of Measures is that they are a feature to let the compiler verify that your arithmetic logic is sound so you do not end up for instance adding Yens + Euros. For that to work you need to have values with specific UoMs. If they were to be generic then the compiler cannot help you anymore and they lose their usefulness. So, there are very few things you can do with generic UoMs.
    – AMieres
    Nov 20 at 14:08








1




1




This seems to be consistent with the general usage of type parameters; for example, if you have a function returning a 'a list, you cannot return a float list from one branch and a int list from another branch. It might work if you declare your function getFx1 as inline (as the compiler will then use statically resolved type parameters).
– dumetrulo
Nov 20 at 12:50






This seems to be consistent with the general usage of type parameters; for example, if you have a function returning a 'a list, you cannot return a float list from one branch and a int list from another branch. It might work if you declare your function getFx1 as inline (as the compiler will then use statically resolved type parameters).
– dumetrulo
Nov 20 at 12:50






1




1




The thing with Unit of Measures is that they are a feature to let the compiler verify that your arithmetic logic is sound so you do not end up for instance adding Yens + Euros. For that to work you need to have values with specific UoMs. If they were to be generic then the compiler cannot help you anymore and they lose their usefulness. So, there are very few things you can do with generic UoMs.
– AMieres
Nov 20 at 14:08




The thing with Unit of Measures is that they are a feature to let the compiler verify that your arithmetic logic is sound so you do not end up for instance adding Yens + Euros. For that to work you need to have values with specific UoMs. If they were to be generic then the compiler cannot help you anymore and they lose their usefulness. So, there are very few things you can do with generic UoMs.
– AMieres
Nov 20 at 14:08












1 Answer
1






active

oldest

votes

















up vote
9
down vote



accepted










The problem is that you're trying to define a function that takes a string and returns a value of type either FxUnit<USD,USD> or FxUnit<USD,EUR>. A function can't have two different return types, decided at runtime.



You could make FxUnit take two values of a discriminated union instead of measures:



type Currency =
| USD
| JPY
| EUR

type FxUnit = { UnitRate : float; From : Currency; To : Currency }

let getFx1 u =
match u with
| "USD" -> {UnitRate = 1.0; From = USD; To = USD}
| "EUR" -> {UnitRate = 1.0; From = USD; To = EUR}
| _ -> failwithf "Unrecognised units %s" u





share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53391628%2fissue-with-generic-unit-of-measures-match%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    9
    down vote



    accepted










    The problem is that you're trying to define a function that takes a string and returns a value of type either FxUnit<USD,USD> or FxUnit<USD,EUR>. A function can't have two different return types, decided at runtime.



    You could make FxUnit take two values of a discriminated union instead of measures:



    type Currency =
    | USD
    | JPY
    | EUR

    type FxUnit = { UnitRate : float; From : Currency; To : Currency }

    let getFx1 u =
    match u with
    | "USD" -> {UnitRate = 1.0; From = USD; To = USD}
    | "EUR" -> {UnitRate = 1.0; From = USD; To = EUR}
    | _ -> failwithf "Unrecognised units %s" u





    share|improve this answer

























      up vote
      9
      down vote



      accepted










      The problem is that you're trying to define a function that takes a string and returns a value of type either FxUnit<USD,USD> or FxUnit<USD,EUR>. A function can't have two different return types, decided at runtime.



      You could make FxUnit take two values of a discriminated union instead of measures:



      type Currency =
      | USD
      | JPY
      | EUR

      type FxUnit = { UnitRate : float; From : Currency; To : Currency }

      let getFx1 u =
      match u with
      | "USD" -> {UnitRate = 1.0; From = USD; To = USD}
      | "EUR" -> {UnitRate = 1.0; From = USD; To = EUR}
      | _ -> failwithf "Unrecognised units %s" u





      share|improve this answer























        up vote
        9
        down vote



        accepted







        up vote
        9
        down vote



        accepted






        The problem is that you're trying to define a function that takes a string and returns a value of type either FxUnit<USD,USD> or FxUnit<USD,EUR>. A function can't have two different return types, decided at runtime.



        You could make FxUnit take two values of a discriminated union instead of measures:



        type Currency =
        | USD
        | JPY
        | EUR

        type FxUnit = { UnitRate : float; From : Currency; To : Currency }

        let getFx1 u =
        match u with
        | "USD" -> {UnitRate = 1.0; From = USD; To = USD}
        | "EUR" -> {UnitRate = 1.0; From = USD; To = EUR}
        | _ -> failwithf "Unrecognised units %s" u





        share|improve this answer












        The problem is that you're trying to define a function that takes a string and returns a value of type either FxUnit<USD,USD> or FxUnit<USD,EUR>. A function can't have two different return types, decided at runtime.



        You could make FxUnit take two values of a discriminated union instead of measures:



        type Currency =
        | USD
        | JPY
        | EUR

        type FxUnit = { UnitRate : float; From : Currency; To : Currency }

        let getFx1 u =
        match u with
        | "USD" -> {UnitRate = 1.0; From = USD; To = USD}
        | "EUR" -> {UnitRate = 1.0; From = USD; To = EUR}
        | _ -> failwithf "Unrecognised units %s" u






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 20 at 13:14









        marklam

        4,80511620




        4,80511620






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53391628%2fissue-with-generic-unit-of-measures-match%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            404 Error Contact Form 7 ajax form submitting

            How to know if a Active Directory user can login interactively

            Refactoring coordinates for Minecraft Pi buildings written in Python