El De-dog-lo

@isislovecruft I'm having this issue to, did you have a workaround?

I don't think that you should have to specify the amount of bits the type takes up. We can calculate that.

It would be really nice if we have the ability to create custom types (or type aliases) such that we could allow typing to be used by end users more...

Note: 38 decimal places is the most possible that can fit in 128 bits (corresponding to `fixed255x38`)

List of decimals: 1. `fixed132x1` 1. `fixed135x2` 1. `fixed138x3` 1. `fixed142x4` 1. `fixed145x5` 1. `fixed148x6` 1. `fixed152x7` 1. `fixed155x8` 1. `fixed158x9` 1. `fixed162x10` 1. `fixed165x11` 1. `fixed168x12` 1. `fixed172x13` 1....

Meeting notes: Pamp it

Was thinking about this some more today. It could be something like the following: 1. Internally, Vyper users only see the `Decimal` type, which is a fixed point type that...

Note: might be best to add this feature via #1230 ruleset switch so there it fails to compile under pre-Istanbul rules

We shouldn't have to make it so configurable. It should look more like: ``` blake2b(msg: Bytes) -> bytes32[2] blake2s(msg: Bytes) -> bytes32 ``` I think it's 9 rounds for `blake2b`...

> > Please also include the `blake2s` hashing function. > > coming up to speed on this -- how to calculate `blake2s`? is it somehow derivable from `blake2b_f` (which, just...