# Uninformative syntax error message for unfinished / unmatched let binding

**URL:** <https://discuss.ocaml.org/t/uninformative-syntax-error-message-for-unfinished-unmatched-let-binding/13058>\
**Category:** Community\
**Created:** [September 20, 2023, 12:03pm UTC](https://discuss.ocaml.org/t/uninformative-syntax-error-message-for-unfinished-unmatched-let-binding/13058 "2023-09-20T12:03:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lukstafi](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/lukstafi/32/3442_2.png) [@lukstafi](https://discuss.ocaml.org/u/lukstafi)\
**Post date:** [September 20, 2023, 12:03pm UTC](https://discuss.ocaml.org/t/uninformative-syntax-error-message-for-unfinished-unmatched-let-binding/13058/1 "2023-09-20T12:03:24Z")

</div>

As evidenced by beginner questions, it’s an impactful issue, but I also stumbled on it for a coupe minutes. The editor gives me the following tooltip:

```plaintext
Syntax error dune
Syntax error, expecting `in' ocamllsp

```

So, `ocamllsp` is trying harder. Originally, I’m getting a top-level let keyword highlighted as the error location, if I insert a `;;` then it gets highlighted. Any chance we could get a `this let-binding might be unmatched` pointer?

Apologies as this must have been suggested before although I cannot find it discussed – why I write here instead of filing an feature request issue directly.