reduce) {\n  .carousel-control-prev,\n  .carousel-control-next {\n    transition: none;\n  }\n}\n\n.carousel-control-prev:hover, .carousel-control-prev:focus,\n.carousel-control-next:hover,\n.carousel-control-next:focus {\n  color: #ffffff;\n  text-decoration: none;\n  outline: 0;\n  opacity: 0.9;\n}\n\n.carousel-control-prev {\n  left: 0;\n}\n\n.carousel-control-next {\n  right: 0;\n}\n\n.carousel-control-prev-icon,\n.carousel-control-next-icon {\n  display: inline-block;\n  width: 20px;\n  height:...

pkg database/sql/driver, type Result interface, RowsAffected() (int64, error)
pkg database/sql/driver, type Rows interface { Close, Columns, Next }
pkg database/sql/driver, type Rows interface, Close() error
pkg database/sql/driver, type Rows interface, Columns() []string
pkg database/sql/driver, type Rows interface, Next([]Value) error
pkg database/sql/driver, type RowsAffected int64

    may be on a different server (operated by you or a third party)
    that supports equivalent copying facilities, provided you maintain
    clear directions next to the object code saying where to find the
    Corresponding Source.  Regardless of what server hosts the
    Corresponding Source, you remain obligated to ensure that it is

pkg syscall (windows-386), type AddrinfoW struct, Family int32
pkg syscall (windows-386), type AddrinfoW struct, Flags int32
pkg syscall (windows-386), type AddrinfoW struct, Next *AddrinfoW
pkg syscall (windows-386), type AddrinfoW struct, Protocol int32
pkg syscall (windows-386), type AddrinfoW struct, Socktype int32
pkg syscall (windows-386), type GUID struct