Make ExoPlayerImpl an ExoPlayer implementation
All the functionality of SimpleExoPlayer has moved to ExoPlayerImpl. Hence, ExoPlayerImpl can fulfil its own name and become an ExoPlayer implementation. As a result, ExoPlayer.Builder can return ExoPlayerImpl directly without using SimpleExoPlayer at all. PiperOrigin-RevId: 427947028
This commit is contained in:
parent
b271469fd0
commit
66dfb7361f
@ -958,7 +958,9 @@ public interface ExoPlayer extends Player {
|
|||||||
* @throws IllegalStateException If this method has already been called.
|
* @throws IllegalStateException If this method has already been called.
|
||||||
*/
|
*/
|
||||||
public ExoPlayer build() {
|
public ExoPlayer build() {
|
||||||
return buildSimpleExoPlayer();
|
checkState(!buildCalled);
|
||||||
|
buildCalled = true;
|
||||||
|
return new ExoPlayerImpl(/* builder= */ this, /* wrappingPlayer= */ null);
|
||||||
}
|
}
|
||||||
|
|
||||||
/* package */ SimpleExoPlayer buildSimpleExoPlayer() {
|
/* package */ SimpleExoPlayer buildSimpleExoPlayer() {
|
||||||
|
File diff suppressed because it is too large
Load Diff
Loading…
x
Reference in New Issue
Block a user