I'm submitting a...

[x] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:

Current behavior

Since rxjs@6.0.0 IE10 need polyfill of Object.setPrototypeOf. breaking changes of rxjs6

Angular depends on core-js polyfill. but core-js's Object.setPrototypeOf polyfill needs IE11+ you can check here.

So if Angular want to support IE10. need other polyfill like set-prototype-of or else.

Or just add commented module import syntax like classlist.js.

Or don't support IE10... 😢

Expected behavior

Minimal reproduction of the problem with instructions

After uncomment some lines in polyfill.ts for supporting IE10 but. If browser ran rxjs's EmptyError.js or ArgumentOutOfRangeError.js. throw is not function error.

You can see the source codes

https://github.com/ReactiveX/rxjs/blob/d0ea152f3c5575455a73cc43b8fad6a750d24208/src/internal/util/ArgumentOutOfRangeError.ts#L17

https://github.com/ReactiveX/rxjs/blob/d0ea152f3c5575455a73cc43b8fad6a750d24208/src/internal/util/EmptyError.ts#L17

What is the motivation / use case for changing the behavior?

Environment

Angular version: 6.0.4


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [x] IE version 10 (modern.ie)
- [ ] Edge version XX
 
For Tooling issues:
- Node version: 8.9.3  
- Platform: Windows  

Others: