Skip to content

Update from original#1

Merged
Bolpat merged 1171 commits intoBolpat:masterfrom
dlang:master
Jan 15, 2017
Merged

Update from original#1
Bolpat merged 1171 commits intoBolpat:masterfrom
dlang:master

Conversation

@Bolpat
Copy link
Owner

@Bolpat Bolpat commented Jan 15, 2017

No description provided.

yebblies and others added 30 commits November 17, 2016 19:56
fix Issue 16661 - failing dstring/wstring format string
Use auto instead of ReverseTupleType as that is private.
On some FreeBSD the unittest timeout with increased frequency, hence this change.
The LREFs were broken. Could fix that with underscores, but the links would
just point back at the current section. There's no point in having such
links.
Fix issue 16705 - TaskPool.reduce fails to compile "cannot get frame pointer to D main"
Make std.container.rbtree.RedBlackTree._add @safe
Fix issue 16663: std.unit.toUpper rejects an alias this to a string
Merge remote-tracking branch 'upstream/stable' into merge_stable
fix Issue 16667 - wrong @safe unittest compilation error
DDOX doesn't do auto-highlighting, but the symbols need to be formatted as
code there, too.
Fix Issue 16611 - 'Unrecognized type const(void)' error for std.trait…
This avoids internal error messages in VariantN.this.
[trivial] std.conv: Don't allow to!T() in constraint
Use specialization to prefer to!S when S is a static array.
Add VariantN.opIndexOpAssign.
Also undocument & tweak test for const(Variant).opIndex.
Really fix Issue 16478 - Don't allow to!T() in constraint
Technically, prior to this change, it was possible to define popFront
and popBack to be callables that required parens - such as member
variable with an overloaded opCall or a delegate. It's unlikely that
anyone has actually declared popFront or popBack in this manner, but
it's possible. Because of that, calling popFront or popBack without
parens would technically not work with some valid ranges (even if such
ranges are unlikely to exist) and thus without this change, it's
arguably not valid to call popFront or popBack without parens in generic
code - especially in the standard library.

Andrei wants to be able to call popFront without parens in generic code,
and when I pointed out the existing problem with that, he wanted me to
change it so that it's no longer legal to have a range where popFront or
popBack is a callable that requires parens. So, this PR fixes that.

Now, technically, this is a breaking change, but it's highly unlikely
that it actually breaks any code, and I don't know of any way to do this
change in a way which would allow for any kind of deprecation message
for anyone trying to declare a range with a popFront or popBack that
would not work without parens. So, as far as I can tell, if we want to
make this change, we're stuck making a breaking change, but the odds of
it actually mattering seem low.
MartinNowak and others added 29 commits January 7, 2017 01:03
remove bitwise documentation
Make more modules publicly runnable on dlang.org
merged-on-behalf-of: Martin Nowak <code@dawg.eu>
- use slicing by 8 algorithm with bigger precomputed tables
- roughly 4x faster
* Expand some docs.
* Document (Ref)Appender.T as it's used in public method signatures.
* Document RefAppender.opDispatch.
* Inline undocumented AppenderType.
* Rename appender(E[]*) parameter -> arrayPtr to better distinguish from
  appender(E[]).
Also avoids private symbols in RefAppender constraint.
* Fix ddoc for commented out `this(this)` showing in `put`'s docs.
* Fix missing ddoc for `put(CT[])` due to private `CT`.
* Use documented unittest for scopeBuffer instead of inline code.
Improve docs for Appender, RefAppender
Tweak std.internal.scopebuffer docs
CircleCi: use master as fallback for DMD and Druntime
Also fix order of constraint tests.
Slight optimization for std.conv.text/wtext/dtext
Tweak std.traits function-related docs
merged-on-behalf-of: Sebastian Wilzbach <sebi.wilzbach@gmail.com>
Bitwise cleanup: Fix opSlice index error. Add unittests and changelog entry
I was getting sick of this not working, and there have been multiple bug
reports on this, so I'm just fixing it. With these changes, using == and
!= on null Nullables will not result in an AssertError but instead will
consider them equal if they're both null, equal if they're both non-null
and have the same value, and not equal otherwise.
Fix issue #13017: opEquals for null std.typecons.Nullable
Merge remote-tracking branch 'upstream/stable' into merge_stable
@Bolpat Bolpat merged commit d1ad0cd into Bolpat:master Jan 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.