Use Tensor `Ring` instance instead of `fmap (*)` for CycRep #26

crockeea · 2016-10-20T03:43:46Z

Additive and Ring instances for CycRep currently define (*) = fmap (*). This could be (is?) much slower than letting individual Tensor instances define their own instances. Instead, we should add an entailment for Additive and Ring (any others?) so that CycRep's instances simply call the corresponding tensor instance.

The text was updated successfully, but these errors were encountered:

cpeikert changed the title ~~Use Tensor Ring instance instead of fmap (*) for UCyc~~ Use Tensor Ring instance instead of fmap (*) for CycRep Aug 16, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Use Tensor `Ring` instance instead of `fmap (*)` for CycRep #26

Use Tensor `Ring` instance instead of `fmap (*)` for CycRep #26

crockeea commented Oct 20, 2016 •

edited by cpeikert

Loading

Use Tensor Ring instance instead of fmap (*) for CycRep #26

Use Tensor Ring instance instead of fmap (*) for CycRep #26

Comments

crockeea commented Oct 20, 2016 • edited by cpeikert Loading

Use Tensor `Ring` instance instead of `fmap (*)` for CycRep #26

Use Tensor `Ring` instance instead of `fmap (*)` for CycRep #26

crockeea commented Oct 20, 2016 •

edited by cpeikert

Loading