enable conversion for Map NonList|NonRecord Any

[DrSensor]

I've just noticed that dhall-to-yaml doesn't transform Map Natural Text which I use to define .sublime-syntax match patterns (by converting List/indexed into Map)

block-comment:
  - captures:
    - mapKey: 1
      mapValue: punctuation.definition.comment.scl.scl
    match: (/\*)(?:\s*(?=\s|(\*/)))?
    push:
    - meta_scope: comment.block
    - pop: true
      captures:
      - mapKey: 0
        mapValue: punctuation.definition.comment.scl.scl
      match: \*/

Unlike JSON, key in YAML can be any type except List and Record, which are:

• Text
• Natural
• Integer
• Double
• Bool
• Optional Type, except List and Record
• Union Type, except List and Record

Also, some key type that I think need to be converted too on dhall-to-json:

• None Text, --omitEmpty will delete record field
• Some Text
• let any_Union_that_has = < T1: Text | T2: Optional Text | T3 >
• Text

[sjakobi]

To be clear: You'd like your example to be converted like this?

block-comment:
  - captures:
      1: punctuation.definition.comment.scl.scl
    match: (/\*)(?:\s*(?=\s|(\*/)))?
    push:
    - meta_scope: comment.block
    - pop: true
      captures:
        0: punctuation.definition.comment.scl.scl
      match: \*/
`

[DrSensor]

Yes

[sjakobi]

Work on this issue should probably wait for the switch to aeson-yaml as planned in #1248 (comment).

[sjakobi]

If we want to generate and parse YAML with non-Text keys, we will have to move away from the current Dhall-JSON-YAML pipeline, where Dhall expressions are first encoded as JSON and then translated to YAML. It would probably make sense to move the HsYAML-based logic to a separate package dhall-yaml(?) then. The aeson-yaml-based code could possibly stay in dhall-json. In any case it would be nice to get rid of the gpl flag again.

[sjakobi]

I have made a separate issue for discussing dhall-yaml: #1435.