Lib fmt

Module editing plan template

1. Announcement to mailing list

• Proposed editor: your name
• Date proposed: date of proposal
• Link: link to email

Notes from discussion on mailing list

• "RFC: User-implementable format specifiers w/ compile-time checks" 2013-05-03
• "Redesigning fmt!" 2013-07-26
• Some notes in "bikeshedding println() and friends"

2. Research of standards and techniques

1. Standard: standard - link to docs - ...
2. Standard: standard - link to docs - ...
3. Technique: ICU/Java-stype MessageFormat - http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/MessageFormat.html - http://docs.oracle.com/javase/1.4.2/docs/api/java/text/MessageFormat.html

Summary of research on standards and leading techniques

Relevant standards and techniques exist?

Those intended to follow (and why)

Something like the MessageFormat specifier should be our default, given that it's the leading approach to the needs of i18n.

Those intended to ignore (and why)

3. Research of libraries from other languages

1. Language: C++ - boost format
2. Language: Java - java.text.MessageFormat - java.util.Formatter
3. Language: Common Lisp - Format
4. Language: Python 3 - Format strings
5. Language: C/POSIX - ICU MessageFormat - Printf
6. Language: C#/.NET - Formatting types
7. Language: Go - go.fmt
8. Language: JS - MessageFormat.js

Summary of research from other languages:

Structures and functions commonly appearing

Variations on implementation seen

Pitfalls and hazards associated with each variant

Relationship to other libraries and/or abstract interfaces

4. Module writing

• Pull request: link to bug

Additional implementation notes

• note
• note
• note