We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've talked two active users (in early stage).
There are various opinions regarding using native Python structure (List/Dict/Tuple) to model deal.
Current design with native structure may look appearing or nuance trouble , when the solution is being integrated in big part of system.
While, for scripting users , it would be great to have a "typed" info to avoid duplicate typing and IDE friendly ( also ,LLM-assist friendly )
The potential solution I"m thinking of is
Different options have varius resource impact and , the most important, backward compatibility
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I've talked two active users (in early stage).
There are various opinions regarding using native Python structure (List/Dict/Tuple) to model deal.
Current design with native structure may look appearing or nuance trouble , when the solution is being integrated in big part of system.
While, for scripting users , it would be great to have a "typed" info to avoid duplicate typing and IDE friendly ( also ,LLM-assist friendly )
The potential solution I"m thinking of is
Different options have varius resource impact and , the most important, backward compatibility
The text was updated successfully, but these errors were encountered: