Sometimes it just needs a nudge in the right direction (thanks @jc00ke@hachyderm.io on fosstodon!). I dismissed structs as being too verbose as I need: (1) map-like modeling, (2) types per field, (3) mandatory/optional keys. All possible, but terribly verbose.

But: there's hexdocs.pm/typedstruct

I love #elixirlang. Yet there are some things I struggle with. One if it: typing + reporting of type errors. E.g.: closed map types. Function defined to return `t`, yet returning a `t` plus an additional field. I expected dialyzer to point me to the superfluous field, but it didn't. What do I miss?

So I tried the very neat #MCPServer UI "mcp-inspector", noticing that it kills my server process after the `initialize` message. 🤔
```
Processing MCP Client request: {...,"method":"initialize","params":{"protocolVersion":"2024-11-05",...}}
...
SIGTERM received - shutting down
```
#ElixirLang