Lack of Error Reporting for Unsupported Features

[code-with-parth]

Description:
The translator does not provide clear or detailed error messages when encountering unsupported features in the input shader code. This makes it difficult for developers to identify and debug the root cause of translation failures.

Steps to Reproduce:

1. Write an HLSL shader using unsupported features, such as the groupshared keyword or certain compute shader functionalities.

2. Translate the shader using CrossGL.

3. Observe that the error message is vague or generic, offering little guidance.

Expected Behavior:
The translator should output detailed error messages specifying the exact feature, line number, and potential reasons for failure.

Actual Behavior:
The translator either outputs a generic error message or fails silently, making debugging time-consuming and inefficient.

Environment Details:

OS: Ubuntu 22.04

Python Version: 3.11

Additional Context:

This issue can be resolved by enhancing error handling in the parsing and code generation stages (e.g., lexer.py and parser.py).

Detailed error messages improve developer experience and make the tool more robust.

[code-with-parth]

@CrossGL-issue-bot assign me