Error when using Series.clear on nested Object types

[stinodego]

Checks

• I have checked that this issue has not already been reported.
• I have confirmed this bug exists on the latest version of Polars.

Reproducible example

import polars as pl

s = pl.Series([[object()]], dtype=pl.List(pl.Object()))
s.clear()

Log output

thread '<unnamed>' panicked at /home/stijn/code/polars/crates/polars-core/src/named_from.rs:162:86:
called `Result::unwrap()` on an `Err` value: InvalidOperation(ErrString("`list_builder` operation not supported for dtype `object`"))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Traceback (most recent call last):
  File "/home/stijn/code/polars/py-polars/repro.py", line 11, in <module>
    s = pl.Series([[object()]], dtype=pl.List(pl.Object()))
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/stijn/code/polars/py-polars/polars/series/series.py", line 314, in __init__
    self._s = sequence_to_pyseries(
              ^^^^^^^^^^^^^^^^^^^^^
  File "/home/stijn/code/polars/py-polars/polars/_utils/construction/series.py", line 277, in sequence_to_pyseries
    pyseries = PySeries.new_series_list(name, pyseries_list, strict)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pyo3_runtime.PanicException: called `Result::unwrap()` on an `Err` value: InvalidOperation(ErrString("`list_builder` operation not supported for dtype `object`"))

Issue description

Offending code is here:

polars/crates/polars-core/src/series/mod.rs

Lines 161 to 173 in d7d720a

	pub fn clear(&self) -> Series {
	if self.is_empty() {
	self.clone()
	} else {
	match self.dtype() {
	#[cfg(feature = "object")]
	DataType::Object(_, _) => self
	.take(&ChunkedArray::<IdxType>::new_vec("", vec![]))
	.unwrap(),
	dt => Series::new_empty(self.name(), dt),
	}
	}
	}

Clearly this doesn't account for nested object types.

Expected behavior

Return an empty Series.

Installed versions

main

[stinodego]

@ritchie46 Thanks for the fixing the panic - but the issue has not been fixed yet! This should not error either.

We should be careful not to close panic issues when the underlying issue persists.