Skip to content

Should be an error to specify non-matching kclVersion post-3.0 #13569

Description

@jtran

When the entry-point kclVersion is 3.0-preview or later, it should be an error for an imported file to specify a non-matching kclVersion.

We can relax this constraint in the future, but once it's released, it would be a breaking change to add an error.

We must allow specifying a version so that users can switch between entry-point files. I.e. they can run assembly.kcl and part.kcl, both with kclVersion = "3.0-preview". Until the project.toml setting works, this is the only option.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kclLanguage and compiler featureskcl-back-compatKCL backward compatibility. Please don't deprioritize these issues without consulting the KCL team.

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions