zeroshade commented on code in PR #2:
URL: https://github.com/apache/iceberg-go/pull/2#discussion_r1326134685


##########
partitions.go:
##########
@@ -0,0 +1,218 @@
+// 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.
+
+package iceberg
+
+import (
+       "encoding/json"
+       "fmt"
+       "strings"
+
+       "golang.org/x/exp/slices"

Review Comment:
   Sorry I forgot to respond here on the PR because we ended up discussing this 
in the slack channel. 
   
   Tl;DR: the standard for Go in general is to target N-1 versions (ie. right 
now the latest is Go 1.21, so we want to target Go 1.20 + Go 1.21). This slices 
package was only added to the Go stdlib in Go 1.21, so we still need to point 
at `golang.org/x/exp/slices` until/unless we drop support for Go 1.20, at which 
point we can update this to just use the stdlib version of the package. 
   
   We're still about 6 months or so before Go 1.22 would get released, but this 
should be fine for now. Once Go 1.22 is released I'll replace these with the 
stdlib package, letting us maintain the N-1 compatibility.



-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to