removal of problematic iOS examples #7601
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
about iOS #7458 and #7457 (which i've authored as the "residue" of a crunch in the iOS issues) the examples in question are not necessarily crucial, enlightening nor super up-to-date in terms of their "iOS-best-pratice" design (which the "native" examples attempt to follow).
They can simply be removed, and eventually be replaced by a single example that builds on modern features. The iOS examples are otherwise plentiful and nothing prevents learning enough to pull apps together.
@danoli3 mentions #7457 (comment) the possibility of disabling arc on some components; that's OK to strong-arm old code, but needing to tweak the .xcodeproj after the PG generation does note make a good "example"...
so this "closes" #7458 and #7457