[dart-misc] Whence the DEP meeting notes?

['Bob Nystrom' via Dart Misc]

Greetings, Dartisans!

You may be wondering why there's been no DEP meeting notes for a few weeks.
Part of that is the holidays, but also it's because we've decided to put
the meetings on ice for a while.

This *doesn't* mean that the *language* is going on ice. On the contrary,
Dart is evolving faster than ever and we felt the meetings were slowing us
down. A short meeting over VC isn't an effective way to do large scale,
meaningful language changes, so we found they tended to be used to either:

1. Give a final yay/nay vote for features that were designed elsewhere.
2. Hash out tiny corner cases and small scale syntactic sugar features.

We don't have any features in the pipeline that are ready for #1 right now
and #2 is an annoying distraction for the important language work that is
happening right now.

A bunch of people on the team are cranking hard on experimental
implementations of *generic methods
<https://github.com/dart-lang/dart_enhancement_proposals/issues/22>*,
*config-specific
code <https://github.com/dart-lang/dart_enhancement_proposals/issues/40>*,
and hopefully soon *non-nullable types
<https://github.com/dart-lang/dart_enhancement_proposals/issues/30>*. Those
are moving along well and we want to let the team focus on those without
also having to worry about other minor language changes.

Cheers!

– bob

[Joel Trottier-Hébert]

good to hear! keep up the good work! :)

On Tue, Jan 5, 2016 at 12:27 PM 'Bob Nystrom' via Dart Misc <

Post by 'Bob Nystrom' via Dart Misc
Greetings, Dartisans!
You may be wondering why there's been no DEP meeting notes for a few
weeks. Part of that is the holidays, but also it's because we've decided to
put the meetings on ice for a while.
This *doesn't* mean that the *language* is going on ice. On the contrary,
Dart is evolving faster than ever and we felt the meetings were slowing us
down. A short meeting over VC isn't an effective way to do large scale,
1. Give a final yay/nay vote for features that were designed elsewhere.
2. Hash out tiny corner cases and small scale syntactic sugar features.
We don't have any features in the pipeline that are ready for #1 right now
and #2 is an annoying distraction for the important language work that is
happening right now.
A bunch of people on the team are cranking hard on experimental
implementations of *generic methods
<https://github.com/dart-lang/dart_enhancement_proposals/issues/22>*, *config-specific
code <https://github.com/dart-lang/dart_enhancement_proposals/issues/40>*,
and hopefully soon *non-nullable types
<https://github.com/dart-lang/dart_enhancement_proposals/issues/30>*.
Those are moving along well and we want to let the team focus on those
without also having to worry about other minor language changes.
Cheers!
– bob
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
---
You received this message because you are subscribed to the Google Groups
"Dart Misc" group.
To unsubscribe from this group and stop receiving emails from it, send an

[Günter Zöchbauer]

Thanks for the update!
Always good to get some hints about the priorities and what's going on in
general.

Post by Joel Trottier-Hébert
good to hear! keep up the good work! :)
On Tue, Jan 5, 2016 at 12:27 PM 'Bob Nystrom' via Dart Misc <

Post by 'Bob Nystrom' via Dart Misc
Greetings, Dartisans!
You may be wondering why there's been no DEP meeting notes for a few
weeks. Part of that is the holidays, but also it's because we've decided to
put the meetings on ice for a while.
This *doesn't* mean that the *language* is going on ice. On the
contrary, Dart is evolving faster than ever and we felt the meetings were
slowing us down. A short meeting over VC isn't an effective way to do large
scale, meaningful language changes, so we found they tended to be used to
1. Give a final yay/nay vote for features that were designed elsewhere.
2. Hash out tiny corner cases and small scale syntactic sugar features.
We don't have any features in the pipeline that are ready for #1 right
now and #2 is an annoying distraction for the important language work that
is happening right now.
A bunch of people on the team are cranking hard on experimental
implementations of *generic methods
<https://github.com/dart-lang/dart_enhancement_proposals/issues/22>*, *config-specific
code <https://github.com/dart-lang/dart_enhancement_proposals/issues/40>*,
and hopefully soon *non-nullable types
<https://github.com/dart-lang/dart_enhancement_proposals/issues/30>*.
Those are moving along well and we want to let the team focus on those
without also having to worry about other minor language changes.
Cheers!
– bob
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
---
You received this message because you are subscribed to the Google Groups
"Dart Misc" group.
To unsubscribe from this group and stop receiving emails from it, send an

[Don Olmstead]

Any issues to follow for the implementations of those specific features
@Bob?

Awesome work! Looking forward to all those things

Post by Günter Zöchbauer
Thanks for the update!
Always good to get some hints about the priorities and what's going on in
general.

Post by Joel Trottier-Hébert
good to hear! keep up the good work! :)
On Tue, Jan 5, 2016 at 12:27 PM 'Bob Nystrom' via Dart Misc <

Post by 'Bob Nystrom' via Dart Misc
Greetings, Dartisans!
You may be wondering why there's been no DEP meeting notes for a few
weeks. Part of that is the holidays, but also it's because we've decided to
put the meetings on ice for a while.
This *doesn't* mean that the *language* is going on ice. On the
contrary, Dart is evolving faster than ever and we felt the meetings were
slowing us down. A short meeting over VC isn't an effective way to do large
scale, meaningful language changes, so we found they tended to be used to
1. Give a final yay/nay vote for features that were designed elsewhere.
2. Hash out tiny corner cases and small scale syntactic sugar features.
We don't have any features in the pipeline that are ready for #1 right
now and #2 is an annoying distraction for the important language work that
is happening right now.
A bunch of people on the team are cranking hard on experimental
implementations of *generic methods
<https://github.com/dart-lang/dart_enhancement_proposals/issues/22>*, *config-specific
code <https://github.com/dart-lang/dart_enhancement_proposals/issues/40>*,
and hopefully soon *non-nullable types
<https://github.com/dart-lang/dart_enhancement_proposals/issues/30>*.
Those are moving along well and we want to let the team focus on those
without also having to worry about other minor language changes.
Cheers!
– bob
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to
http://www.dartbug.com/new
---
You received this message because you are subscribed to the Google
Groups "Dart Misc" group.
To unsubscribe from this group and stop receiving emails from it, send

--

For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
---
You received this message because you are subscribed to the Google Groups
"Dart Misc" group.
To unsubscribe from this group and stop receiving emails from it, send an

['Bob Nystrom' via Dart Misc]

Post by Don Olmstead
Any issues to follow for the implementations of those specific features
@Bob?

Good question. I'm not sure how these are tracked.

- Leaf probably knows the status of generic methods.
- Florian has been working on config-specific code.
- No one is hacking on non-nullable types yet, but hopefully it will get
picked up soon.

Cheers!

– bob

[Lasse Damgaard]

What does this mean for the DEP process, for instance if one wants to
propose a spec change to lift some constraints on the analyzer?
I'm thinking of https://github.com/dart-lang/sdk/issues/25233

Thanks
Lasse

Post by 'Bob Nystrom' via Dart Misc
Greetings, Dartisans!
You may be wondering why there's been no DEP meeting notes for a few
weeks. Part of that is the holidays, but also it's because we've decided to
put the meetings on ice for a while.
This *doesn't* mean that the *language* is going on ice. On the contrary,
Dart is evolving faster than ever and we felt the meetings were slowing us
down. A short meeting over VC isn't an effective way to do large scale,
1. Give a final yay/nay vote for features that were designed elsewhere.
2. Hash out tiny corner cases and small scale syntactic sugar features.
We don't have any features in the pipeline that are ready for #1 right now
and #2 is an annoying distraction for the important language work that is
happening right now.
A bunch of people on the team are cranking hard on experimental
implementations of *generic methods
<https://github.com/dart-lang/dart_enhancement_proposals/issues/22>*, *config-specific
code <https://github.com/dart-lang/dart_enhancement_proposals/issues/40>*,
and hopefully soon *non-nullable types
<https://github.com/dart-lang/dart_enhancement_proposals/issues/30>*.
Those are moving along well and we want to let the team focus on those
without also having to worry about other minor language changes.
Cheers!
– bob

['Bob Nystrom' via Dart Misc]

Post by Lasse Damgaard
What does this mean for the DEP process, for instance if one wants to
propose a spec change to lift some constraints on the analyzer?
I'm thinking of https://github.com/dart-lang/sdk/issues/25233

I think for those kinds of changes, I would see if it's something that we
could support in strong mode, which avoids most of the debate about what
should and shouldn't go in the language spec. It also doesn't require going
through anything like TC52 or the DEP committee.

I added a comment to that bug to that effect.

Cheers!

– bob