This repository has been archived on 2023-08-20. You can view files and clone it, but cannot push or open issues or pull requests.

Fabien Potencier 3471b58318 bug #22496 [DI] Fix inlining conflict by restricting IteratorArgument to Reference[] (nicolas-grekas) ... This PR was merged into the 3.3-dev branch. Discussion ---------- [DI] Fix inlining conflict by restricting IteratorArgument to Reference[] | Q | A | ------------- | --- | Branch? | 3.3 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | - | License | MIT | Doc PR | - `Reference` found in `ArgumentInterface::getValue()` are currently not inlined. While trying to do so (hint: I failed), I noticed that the current code is broken for `IteratorArgument` which can contain anonymous `Definition` for now, which are then not inlined correctly. This PR restricts `IteratorArgument` to arrays of `Reference`, and improves a few related things found while doing it. (fabbot failure is false positive) Commits ------- 4d3dce1c0f [DI] Fix inlining conflict by restricting IteratorArgument to Reference[]		2017-04-23 15:36:34 -07:00
..
Bridge	[DI] Make tagged abstract services throw earlier	2017-04-13 15:45:25 +02:00
Bundle	bug #22494 [Security] Fix json_login default success/failure handling (chalasr)	2017-04-23 15:21:45 -07:00
Component	bug #22496 [DI] Fix inlining conflict by restricting IteratorArgument to Reference[] (nicolas-grekas)	2017-04-23 15:36:34 -07:00