Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Bugzilla Issue 24637 -- [REG 2.104] Cannot insert const/immutable elements into DList #9042

Open
wants to merge 30 commits into
base: stable
Choose a base branch
from

Conversation

RubyTheRoobster
Copy link
Contributor

No description provided.

@dlang-bot
Copy link
Contributor

dlang-bot commented Aug 3, 2024

Thanks for your pull request and interest in making D better, @RubyTheRoobster! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

  • My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
  • My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
  • I have provided a detailed rationale explaining my changes
  • New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.


If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Auto-close Bugzilla Severity Description
14138 major std.parallelism.task breaks @safety
15315 normal can break immutable with std.algorithm.move
20870 normal std.outbuffer.printf is trusted
20872 normal std.array.assocArray trusts user-provided 'front' for values
22293 enhancement Nullable should define opCast!bool
23300 normal std.array : array wrongly propagates scopeness of source
24637 regression [REG 2.104] Cannot insert const/immutable elements into DList
24667 normal goo.gl is going away
24685 major std.stdio.File.rawRead allows reading raw pointers from files in @safe code

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "stable + phobos#9042"

std/container/dlist.d Outdated Show resolved Hide resolved
std/container/dlist.d Outdated Show resolved Hide resolved
std/container/dlist.d Outdated Show resolved Hide resolved
@RubyTheRoobster
Copy link
Contributor Author

BuildKite is failing with:

CMake Error at cmake/Modules/FindLLVM.cmake:62 (message):
  Unsupported LLVM version 14.0.0 found (/bin/llvm-config).  At least version
  15.0 is required.  You can also set variables 'LLVM_ROOT_DIR' or
  'LLVM_CONFIG' to use a different LLVM installation.
Call Stack (most recent call first):
  cmake/Modules/FindLLVM.cmake:190 (_LLVM_FAIL)
  CMakeLists.txt:37 (find_package)

This seems to be a bug.

@kinke
Copy link
Contributor

kinke commented Aug 9, 2024

AFAIK, this depends on @ibuclaw re-creating his Buildkite agents using the latest docker image definition: dlang/ci#489 (comment)

@RazvanN7
Copy link
Collaborator

@RubyTheRoobster maybe a rebase will fix the failing buildkite test.

0-v-0 and others added 11 commits August 20, 2024 22:51
…g#9019)

* Move `std.math.exponential.pow` implementation outside template

* Fix compilation on Mac
Caught with grep -Er '\(\$[A-Za-z]'
for link in $(grep -Eor 'https?://[^\\)", ]+' | grep -v dlang.org \
| grep -Eo 'https?://.+'); do (printf "%s: " "$link"; curl -Is "$link" \
| head -n1) | grep -E '4..$'; done

for link in $(grep -Eor '\\$\\(HTTP .+, ' | grep -v dlang.org \
| cut -d' ' -f2- | sed 's/, .*$//'); do out="$(curl -Is "$link")"; \
(! [ $? = 0 ] || printf '%s' "$out" | head -n1 | grep -Eq '4..') \
&& printf '%s\\n' "$link"; done
Note: www.canonware.com/download/jemalloc/jemalloc-latest/doc/jemalloc.html jemalloc link isn't responding, and it now lives at jemalloc.net (see also https://github.com/jemalloc/jemalloc?tab=readme-ov-file#readme).

Fixes Bugzilla Issue 24667 - goo.gl is going away.
@RubyTheRoobster
Copy link
Contributor Author

I have never had to perform a rebase before, so I have no idea if all of the extra commits are acceptable or not.

@CyberShadow
Copy link
Member

Unfortunately no, they are an indication that something went wrong with the rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.