How to avoid repetitive long generic constraints in Rust





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







11















I'm trying to make my own implementation of big integers (just for education). The implementation is generic by data type:



struct LongNum<T>
where T: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8>
{
values: Vec<T>,
powers: Vec<u8>,
radix: u8,
}


The problem is that I need to repeat this verbose constraint for T in all impls. It's too cumbersome.



I can make my own trait combining these constraints, like this:



trait LongNumValue: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8> {}

struct LongNum<T: LongNumValue>
{
values: Vec<T>,
powers: Vec<u8>,
radix: u8,
}


But in this case I have to add impls for this LongNumValue trait to all types which can be used in LongNum:



impl LongNumValue for u8 {}
impl LongNumValue for u16 {}
impl LongNumValue for u32 {}
...


This means that if I don't add some type to this list of impls, the user of my crate will be unable to use this type for LongNum, even if this type is passes all constraints.



Is there any way to avoid writing long repetitive costraints without adding unnecessary restrictions to user?










share|improve this question


















  • 1





    You mean something similar to this? stackoverflow.com/questions/55553281/…

    – hellow
    yesterday


















11















I'm trying to make my own implementation of big integers (just for education). The implementation is generic by data type:



struct LongNum<T>
where T: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8>
{
values: Vec<T>,
powers: Vec<u8>,
radix: u8,
}


The problem is that I need to repeat this verbose constraint for T in all impls. It's too cumbersome.



I can make my own trait combining these constraints, like this:



trait LongNumValue: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8> {}

struct LongNum<T: LongNumValue>
{
values: Vec<T>,
powers: Vec<u8>,
radix: u8,
}


But in this case I have to add impls for this LongNumValue trait to all types which can be used in LongNum:



impl LongNumValue for u8 {}
impl LongNumValue for u16 {}
impl LongNumValue for u32 {}
...


This means that if I don't add some type to this list of impls, the user of my crate will be unable to use this type for LongNum, even if this type is passes all constraints.



Is there any way to avoid writing long repetitive costraints without adding unnecessary restrictions to user?










share|improve this question


















  • 1





    You mean something similar to this? stackoverflow.com/questions/55553281/…

    – hellow
    yesterday














11












11








11








I'm trying to make my own implementation of big integers (just for education). The implementation is generic by data type:



struct LongNum<T>
where T: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8>
{
values: Vec<T>,
powers: Vec<u8>,
radix: u8,
}


The problem is that I need to repeat this verbose constraint for T in all impls. It's too cumbersome.



I can make my own trait combining these constraints, like this:



trait LongNumValue: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8> {}

struct LongNum<T: LongNumValue>
{
values: Vec<T>,
powers: Vec<u8>,
radix: u8,
}


But in this case I have to add impls for this LongNumValue trait to all types which can be used in LongNum:



impl LongNumValue for u8 {}
impl LongNumValue for u16 {}
impl LongNumValue for u32 {}
...


This means that if I don't add some type to this list of impls, the user of my crate will be unable to use this type for LongNum, even if this type is passes all constraints.



Is there any way to avoid writing long repetitive costraints without adding unnecessary restrictions to user?










share|improve this question














I'm trying to make my own implementation of big integers (just for education). The implementation is generic by data type:



struct LongNum<T>
where T: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8>
{
values: Vec<T>,
powers: Vec<u8>,
radix: u8,
}


The problem is that I need to repeat this verbose constraint for T in all impls. It's too cumbersome.



I can make my own trait combining these constraints, like this:



trait LongNumValue: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8> {}

struct LongNum<T: LongNumValue>
{
values: Vec<T>,
powers: Vec<u8>,
radix: u8,
}


But in this case I have to add impls for this LongNumValue trait to all types which can be used in LongNum:



impl LongNumValue for u8 {}
impl LongNumValue for u16 {}
impl LongNumValue for u32 {}
...


This means that if I don't add some type to this list of impls, the user of my crate will be unable to use this type for LongNum, even if this type is passes all constraints.



Is there any way to avoid writing long repetitive costraints without adding unnecessary restrictions to user?







generics rust constraints traits






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked yesterday









Michael IlyinMichael Ilyin

13427




13427








  • 1





    You mean something similar to this? stackoverflow.com/questions/55553281/…

    – hellow
    yesterday














  • 1





    You mean something similar to this? stackoverflow.com/questions/55553281/…

    – hellow
    yesterday








1




1





You mean something similar to this? stackoverflow.com/questions/55553281/…

– hellow
yesterday





You mean something similar to this? stackoverflow.com/questions/55553281/…

– hellow
yesterday












1 Answer
1






active

oldest

votes


















18














You can add a blanket implementation:



impl<T> LongNumValue for T 
where
T: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8> {}





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',
    autoActivateHeartbeat: false,
    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%2f55568655%2fhow-to-avoid-repetitive-long-generic-constraints-in-rust%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









    18














    You can add a blanket implementation:



    impl<T> LongNumValue for T 
    where
    T: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8> {}





    share|improve this answer




























      18














      You can add a blanket implementation:



      impl<T> LongNumValue for T 
      where
      T: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8> {}





      share|improve this answer


























        18












        18








        18







        You can add a blanket implementation:



        impl<T> LongNumValue for T 
        where
        T: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8> {}





        share|improve this answer













        You can add a blanket implementation:



        impl<T> LongNumValue for T 
        where
        T: Integer + MulAssign + CheckedMul + CheckedAdd + Copy + From<u8> {}






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered yesterday









        starbluestarblue

        45.6k1177138




        45.6k1177138
































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55568655%2fhow-to-avoid-repetitive-long-generic-constraints-in-rust%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

            How to label and detect the document text images

            Vallis Paradisi

            Tabula Rosettana