`moore` function in Clash

Clash Help
1

I am confused by how moore function has been defined in Clash. Shouldn’t moore machines depend only on it’s current state?

Something like:

mooreMachine :: (HiddenClockResetEnable dom, NFDataX s) => (s -> s) -> s -> Signal dom s
mooreMachine transitionFx initialState = currentState
    where 
        currentState = register initialState nextState
        nextState = transitionFx <$> currentState

image
image2176×1230 223 KB

2

Only the output of a moore machine depends on it’s current state. In contrast with mealy where the output can depend on both the current state and the input. In both cases you have an input and an output that is possibly distinct from the state.

This can be soon in the clash moore function as it takes a function of type s -> o. It takes the current states and produces the output. In your version of moore the output is the state and there is no input. This is way more restrictive then a moore.

2 Likes