Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
| No. |
Time |
User |
SHA256 |
| -r1 (urbit-hob-0.1.1-r1) |
2019-09-13T21:28:58Z |
JaredTobin |
a83462610028b959eae411670f4abf010c9645ae378227d54ec634c2dc4a06f3
|
|
Changed description
from Here you can primarily find functions for dealing with the \"patp\" phonetic
base used by Urbit. The \@p encoding is used for naming ships; it uniquely
represents a 32-bit number in a memorable and pronounceable fashion.
The \@p encoding is an obfuscated representation of an underlying 32-bit
number, in particular, hence the \"ob\" in the library's name.
The @Urbit.Ob@ module exposes two functions, 'patp' and 'fromPatp', for
converting between representations. You can render a 'Patp' value via the
'render' function.
Here's a quick example:
> import qualified Urbit.Ob as Ob
>
> let nidsut = Ob.patp 15663360
> Ob.render nidsut -- "~nidsut-tomdun"
> Ob.fromPatp nidsut -- 15663360
to Here you can primarily find functions for dealing with the \"patp\" phonetic
base used by Urbit. The \@p encoding is used for naming ships; it uniquely
represents a 32-bit number in a memorable and pronounceable fashion.
The \@p encoding is an obfuscated representation of an underlying 32-bit
number, in particular, hence the \"ob\" in the library's name.
The @Urbit.Ob@ module exposes two functions, 'patp' and 'fromPatp', for
converting between representations. You can render a 'Patp' value via the
'render' function.
Here's a quick example:
>>> import qualified Urbit.Ob as Ob
>>> let nidsut = Ob.patp 15663360
>>> Ob.render nidsut
"~nidsut-tomdun"
>>> Ob.fromPatp nidsut
15663360
|
| -r0 (urbit-hob-0.1.1-r0) |
2019-09-13T21:24:37Z |
JaredTobin |
d868c5665a57717f6f5b68f8d23d995c96b4e62d2ba45eb727e1f003a8e11bf3
|
|
|