Discussion: Inline code block disabled

Currently, to make a code block in a message, the 3 backticks on each end have to be on a new line.
I don't mind it being that way but when importing messages from slack, slack supports inline code blocks (same with github) and they do not convert correctly.
Is this an intended feature?
Maybe inline full code blocks should be supported?

Example:

This works in chat:

```
{
    "code": "block"
}
```

This does not work:

```{
    "code": "block"
}```

No file or test entry point is named in the report. Reproduce the two fenced-code examples, then trace the message formatting path used for imported Slack content; done means inline fences render as a full code block without regressing line-delimited fences, with coverage for both examples.