dart-lang / dart-lang/language

Why are implicit tear-offs discouraged?

Open
#3,548 2 comments 1 reaction 0 assignees View on GitHub
request
Dominant language
TeX
Stars
2.9k
Forks
239
Avg merge
2d 18h
Merged PRs (30d)
14

Description

Why do I suddenly get lints about https://dart.dev/tools/linter-rules/implicit_call_tearoffs? Doesn't that contradict the language feature of callable classes? Especially for my flutter_command package this is really ugly like:

![grafik](https://github.com/dart-lang/language/assets/16635729/a2a3631d-8392-454b-ad34-6f581866d354)

Contributor guide

Open the contributing guide

Research direction

Start with the linked implicit_call_tearoffs lint rule and the callable-classes behavior shown in the issue. Read the existing discussion and language documentation to determine whether the rationale or guidance is missing. Done would mean a clear, agreed explanation of why the lint is recommended and how callable classes should be used.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart
Domain
compilers
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.