[8910]Fixed doc test with feature prettyprint

[manishkr]

Which issue does this PR close?

We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax.

• Closes cargo test -p arrow-cast fails on main #8910 .

Rationale for this change

To fix the doc-test with feature-flag prettyprint

What changes are included in this PR?

Enabled feature-flag prettyprint for specific doc-test that need this feature.

Are these changes tested?

Yes

Are there any user-facing changes?

No

[Jefffrey]

Is there a way to do it so it doesn't show up in the doc like this?

[manishkr]

Is there a way to do it so it doesn't show up in the doc like this?

I am not aware of any such method, but I think showing it clearly in doc may help the user, it shows caller need to use with enabling prettyprint feature flag.

[Jefffrey]

The documentation above it already mentions need for prettyprint feature so it should cover that point.

Perhaps we can try something like this? https://users.rust-lang.org/t/how-to-enable-a-feature-flag-in-a-doc-test/116563/2

[manishkr]

The documentation above it already mentions need for prettyprint feature so it should cover that point.

Perhaps we can try something like this? https://users.rust-lang.org/t/how-to-enable-a-feature-flag-in-a-doc-test/116563/2

Thanks for suggestion, pushed changes with fix.

[alamb]

I ran cargo test -p arrow-cast locally and it passes for me now on this branch ❤️

Thanks @manishkr and @Jefffrey