Rust 2018 All Hands!

[aturon]

Friday recap

A surprise talk from Marijn!

Website

• follow up to previous meeting
• CLI team spent time working on their showcase code example
• Docs teams kicked off content discovery and organization work
• Embedded team explored other “embedded technology” sites for inspiration
• http://rust-wubwub.herokuapp.com/

Compiler

• Explored RLS integration
  • Why RLS isn’t using incremental compilation yet?
    • No real reason… we’re going to try!
  • How can we refine APIs to make this integration better
• Action items (i.e., for eddyb)
• Contributor and mentoring experience for the compiler

WG: net

• Covered a few issues around async/await and lifetimes and “off-by-one” errors around borrowing/owning values
• Surveyed syntactic design space around async blocks & functions
• Discussed ways to implement task::context inside libcore

Tools - IDE planning

• https://github.com/nrc/dev-tools-team/blob/master/berlin-2018/ide-planning.md
• compiler code completion is a long way off, but perhaps some partial solution
  • need to maintain Racer
• testing infrastructure
• debug mode
• new features - pick low-hanging fruit from codegen/refactoring/module auto-imports

Libs

• Large amount of triage
  • Regressions in 1.26 (which is soon going into beta)
  • Long list of outstanding issues
    • name for the simd module
      • std::arch
    • global allocator trait design
    • “needs decision” issues

Lang

• Talked about extern type and its interaction with size_of_val
  • Thoughts are on the thread, tldr want to stabilize soon
• Discussed a possible RFC around #[derive(Ord)] and friends
  • targeting new edition
• Discussed mitigation strategies around regressions arising from new AsRef impls
  • TLDR: let’s make this better by finding a good syntax for type ascription
• Discussed how we can make using dyn Trait better
  • Grand plans came crashing down
  • Maybe we can use a proc macro to autogenerate some boilerplate…
• Discussed “best practices”
  • Had idea of creating a sort of cross-cutting Guidelines effort:
    • API Guidelines
    • Style Guidelines
    • Lints

Community (Events Team - Florian!)

Came up with areas of event standards we want to hold, around:

• Diversity Outreach
• speaker support and quality
• program guidelines
• review committee guidelines
• communication and transparency (e.g. timelines)
• attendee experience, accessibility and support

We discussed how a relationship between events and us as a project could look like.

Work session produced articles on all topics.

Infra

• Got people selected for the work on the bors plan of action, as well as other high priority things
  • Better docs for the tools infra has and the processes we follow
• We’ve started up new crater machines to handle the excessive productivity from this all hands
• Wish list things
  • Trialling a crater bot (from member of the release team, ‘pietroalbini’)
  • @Tim N is trialling an “extract errors from travis logs” bot (Demo)
• High fives all round, great to meet in person

Cargo

Two related RFCs to write:

• Cargo project templates (needed for WGs)
• Project-scoped cargo subcommands/tasks

Rust Reach

• discussed the goal of bringing new people in and KEEPING them
• how to make people feel like part of a community
  • if you would like to sign up for a 20min chat (video/phone) about what you do for rust with the participants GET IN TOUCH WITH ME (ag_dubs) (may15-aug15)
• https://rust-reach.herokuapp.com/ goes live next monday
  • worked on CLI project
  • worked on embedded project details
  • formed application committee (welcome aidan and diane!)