Hoogle Search
Within LTS Haskell 24.32 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
-
clash-prelude Clash.Explicit.Prelude Synchronizer based on two sequentially connected flip-flops.
- NB: This synchronizer can be used for bit-synchronization.
- NB: Although this synchronizer does reduce metastability,
it does not guarantee the proper synchronization of a whole
word. For example, given that the output is sampled twice as
fast as the input is running, and we have two samples in the input
stream that look like:
[0111,1000]
But the circuit driving the input stream has a longer propagation delay on msb compared to the lsbs. What can happen is an output stream that looks like this:[0111,0111,0000,1000]
Where the level-change of the msb was not captured, but the level change of the lsbs were.If you want to have safe word-synchronization use asyncFIFOSynchronizer.
-
clash-prelude Clash.Explicit.Prelude.Safe Synchronizer based on two sequentially connected flip-flops.
- NB: This synchronizer can be used for bit-synchronization.
- NB: Although this synchronizer does reduce metastability,
it does not guarantee the proper synchronization of a whole
word. For example, given that the output is sampled twice as
fast as the input is running, and we have two samples in the input
stream that look like:
[0111,1000]
But the circuit driving the input stream has a longer propagation delay on msb compared to the lsbs. What can happen is an output stream that looks like this:[0111,0111,0000,1000]
Where the level-change of the msb was not captured, but the level change of the lsbs were.If you want to have safe word-synchronization use asyncFIFOSynchronizer.
-
clash-prelude Clash.Explicit.Signal Special version of delay that doesn't take enable signals of any kind. Initial value will be undefined.
-
clash-prelude Clash.Explicit.Synchronizer Synchronizer based on two sequentially connected flip-flops.
- NB: This synchronizer can be used for bit-synchronization.
- NB: Although this synchronizer does reduce metastability,
it does not guarantee the proper synchronization of a whole
word. For example, given that the output is sampled twice as
fast as the input is running, and we have two samples in the input
stream that look like:
[0111,1000]
But the circuit driving the input stream has a longer propagation delay on msb compared to the lsbs. What can happen is an output stream that looks like this:[0111,0111,0000,1000]
Where the level-change of the msb was not captured, but the level change of the lsbs were.If you want to have safe word-synchronization use asyncFIFOSynchronizer.
dflipflop :: forall (dom :: Domain) a . (HiddenClock dom, NFDataX a) => Signal dom a -> Signal dom aclash-prelude Clash.Prelude Special version of delay that doesn't take enable signals of any kind. Initial value will be undefined.
dflipflop :: forall (dom :: Domain) a . (HiddenClock dom, NFDataX a) => Signal dom a -> Signal dom aclash-prelude Clash.Signal Special version of delay that doesn't take enable signals of any kind. Initial value will be undefined.
rangeGetFlippable :: (HasCallStack, MonadIO m, IsRange a) => a -> m Boolgi-gtk3 GI.Gtk.Objects.Range Gets the value set by rangeSetFlippable. Since: 2.18
rangeSetFlippable :: (HasCallStack, MonadIO m, IsRange a) => a -> Bool -> m ()gi-gtk3 GI.Gtk.Objects.Range If a range is flippable, it will switch its direction if it is horizontal and its direction is TextDirectionRtl. See widgetGetDirection. Since: 2.18
pixbufFlipHorazontally :: Pixbuf -> IO Pixbufgtk Graphics.UI.Gtk.Gdk.Pixbuf No documentation available.
pixbufFlipHorizontally :: Pixbuf -> IO Pixbufgtk Graphics.UI.Gtk.Gdk.Pixbuf Flips a pixbuf horizontally and returns the result in a new pixbuf.