Intentionally defining contractual interfaces to be exported. ⤵️

I'm allowing these contractual interfaces to be exported so they can be
conveniently referenced by calling code. This decision was made after
careful consideration of intended implementation patterns as I actually
coded against the new API, which helped determine that the ability to
reference these type definitions provides significant value.

Author: mdwhatcott

contracts.go

@@ -15,7 +15,6 @@ type (
 
 	// Pool is a common subset of methods implemented by *sql.DB and *sql.Tx.
 	// The name is a nod to that fact that a *sql.DB implements a Pool of connections.
-	// TODO: perhaps un-export?
 	Pool interface {
 		PrepareContext(ctx context.Context, query string) (*sql.Stmt, error)
 		ExecContext(ctx context.Context, query string, args ...any) (sql.Result, error)
@@ -32,7 +31,6 @@ type (
 	}
 
 	// Script represents SQL statements that aren't expected to provide rows as a result.
-	// TODO: perhaps un-export?
 	Script interface {
 		// Statements returns a string containing 1 or more SQL statements, separated by `;`.
 		// This means that the ';' character should NOT be used within any of the statements.
@@ -51,7 +49,6 @@ type (
 
 	// Query represents a SQL statement that is expected to provide rows as a result.
 	// Rows are fed to the Scan method.
-	// TODO: perhaps un-export?
 	Query interface {
 		// Statement returns a string containing a single SQL query.
 		Statement() string