write unhandled-cases-workaround as mentioned in #24 #28

New Issue

2017-05-04T12:51:08+02:00

lspitzner commented

2017-05-04 12:51:08 +02:00

(Migrated from github.com)

There is no content yet.

👍 1

tfausak commented

2019-06-18 19:45:31 +02:00

(Migrated from github.com)

Do this mean automatically passing unknown constructs through? Because the particular case mentioned in #24 (dealing with arrows) can be worked around using --brittany-disable-next-binding. For example:

{-# language Arrows #-}
-- brittany-disable-next-binding
a = proc b -> do
  c <- d -< e
  pure -< f

Do this mean _automatically_ passing unknown constructs through? Because the particular case mentioned in #24 (dealing with arrows) can be worked around using `--brittany-disable-next-binding`. For example: ``` hs {-# language Arrows #-} -- brittany-disable-next-binding a = proc b -> do c <- d -< e pure -< f ```

lspitzner commented

2020-03-16 12:25:10 +01:00

(Migrated from github.com)

Do this mean automatically passing unknown constructs through?

Yes, and this was implemented in d0256bb0db.

> Do this mean automatically passing unknown constructs through? Yes, and this was implemented in d0256bb0dba8d085ef2c19a48b46b79d5159abb0.

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: hexagoxel/brittany#28