Skip to content

Optional static typing for Starlark #7468

Closed as duplicate of#27370
Closed as duplicate of#27370
Optional static typing for Starlark#7468
Assignees
brandjon
Labels
P4This is either out of scope or we don't have bandwidth to review a PR. (No assignee)not staleIssues or PRs that are inactive but not considered staleteam-Starlark-InterpreterIssues involving the Starlark interpreter used by Bazeltype: feature request
@hlopko

Description

@hlopko
hlopko
opened on Feb 19, 2019

Reading #7428 makes me feel like we have worse of both worlds - dynamic typing without dynamic lookup, or static lookup without type safety. If tooling and safety is a goal of Starlark, and it's ok to diverge from Python spec, what is Starlark's team opinion about optional static typing for Starlark?

Metadata

Metadata

Assignees

Labels

P4This is either out of scope or we don't have bandwidth to review a PR. (No assignee)not staleIssues or PRs that are inactive but not considered staleteam-Starlark-InterpreterIssues involving the Starlark interpreter used by Bazeltype: feature request

Type

No type

Projects

Starlark types

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions