summaryrefslogtreecommitdiff
path: root/include/ruby/thread_native.h
diff options
context:
space:
mode:
authorDavid Rodríguez <deivid.rodriguez@riseup.net>2022-10-25 15:21:26 +0200
committerHiroshi SHIBATA <hsbt@ruby-lang.org>2023-11-13 11:06:10 +0900
commit5bdbe242b3034f66157d78f933e6e784326b9720 (patch)
tree61c85c22949bfbef3c7134caef9fbf3fe3aa1161 /include/ruby/thread_native.h
parente2d7e53c5c50fed1df733cf66d353fb1dd90d8f0 (diff)
[rubygems/rubygems] Add a warning in an edge case of using `gemspec` DSL
If a Gemfile duplicates a development dependency also defined in a local gemspec with a different requirement, the requirement in the local gemspec will be silently ignored. This surprised me. I think we should either: * Make sure both requirements are considered, like it happens for runtime dependencies (I added a spec to illustrate the current behavior here). * Add a warning that the requirement in the gemspec will be ignored. I think the former is slightly preferable, but it may cause some bundle's that previously resolve to no longer resolver. I went with the latter but the more I think about it, the more this seems like it should behave like the former. https://github.com/rubygems/rubygems/commit/ad6843972f
Diffstat (limited to 'include/ruby/thread_native.h')
0 files changed, 0 insertions, 0 deletions