alamb commented on code in PR #8290: URL: https://github.com/apache/arrow-rs/pull/8290#discussion_r2337583855
########## arrow-schema/src/datatype_format.rs: ########## @@ -0,0 +1,263 @@ +// Licensed to the Apache Software Foundation (ASF) under one +// or more contributor license agreements. See the NOTICE file +// distributed with this work for additional information +// regarding copyright ownership. The ASF licenses this file +// to you under the Apache License, Version 2.0 (the +// "License"); you may not use this file except in compliance +// with the License. You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, +// software distributed under the License is distributed on an +// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +// KIND, either express or implied. See the License for the +// specific language governing permissions and limitations +// under the License. + +use std::{collections::HashMap, fmt}; + +use crate::DataType; + +impl fmt::Display for DataType { + fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result { + // NOTE: `Display` and `Debug` formatting are ALWAYS the same, Review Comment: I think it is more common in Rust code to have the Debug implementation try and print out something close to the underlying representation, and `Display` is for human consumption Specifically https://doc.rust-lang.org/std/fmt/trait.Debug.html > Debug should format the output in a programmer-facing, debugging context. > > Generally speaking, you should just derive a Debug implementation. vs https://doc.rust-lang.org/std/fmt/trait.Display.html -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
