Difference between revisions of "Language design discussions"
(Revert accidental deletion) |
(→Discussed design issues and free-form proposals) |
||
Line 43: | Line 43: | ||
===== Thread ===== | ===== Thread ===== | ||
* [http://forum.dlang.org/post/nirfuenixutsbgyrcsla@forum.dlang.org auto ref - again] | * [http://forum.dlang.org/post/nirfuenixutsbgyrcsla@forum.dlang.org auto ref - again] | ||
+ | |||
+ | === Built-in associative array issues === | ||
+ | ===== Description ===== | ||
+ | Present AA implementation has lot of problems and most likely needs to be reworked. [[AA_Implementation_Issues]] |
Revision as of 07:45, 19 February 2013
D is an evolving and complex language. New features are proposed, unexpected interaction in old ones get found, design issues are raised. All this may involve hard debates in D newsgroup and if often forgotten. This page serves as an index for major design discussions and proposals.
Contents
Main DIP index
Discussed design issues and free-form proposals
Properties
Description
Initial @property design has issues. How can it be changed or even discarded at all?
Thread
- Initial discussion where this topic has rised
- Walters follow-up with proposal to kill property, most info here
Essential moments
Proposals
Access specifiers and symbol visibility
Description
Currently there is feature like "static global" in C or "unnamed namespace" in C++. Access specifiers for module-level symbols control access, not visibility. Ability to hide symbols needs to be added without breaking current access system.
As a result of discussion, Walter has asked for DIP on this topic.
Essential moments
Thread
- Initial thread that has raised this topic
- Follow-up about current state of affairs
- Access specifiers and visibility - combined data to make a decision upon
Proposal
auto ref
Description
Essential moments
Thread
Built-in associative array issues
Description
Present AA implementation has lot of problems and most likely needs to be reworked. AA_Implementation_Issues