Data race in cached source location information. Shouldn't have a bad impact on things, worst case additional lookups will be done, but should be fixed regardless so it doesn't hit -race testing for consuming libraries.

Instead of just the WithDetail[s] methods, there should convenience methods to add common detail types:

log.String("result", "success").Duration("elapsed", time.Since(t)).Info("call complete")

slog should have examples included in package documentation. Should follow the guidance here: https://blog.golang.org/examples

Including a time field in the JSON messages triggers a bug in the fluentd agent on GCE container optimized OS resulting in the log lines being silently dropped. Fix is to remove that field, which will reduce a bit of functionality for locally running, but will result in no changes when running in the cloud as timestamp is auto-populated at ingest time.

An action should be set up to automate:

• Go generate
• Go format
• Go mod tidy
• Markdown format
• Protobuf format

Action should run on all PR's and commits.

• Go build
• Go/Proto Lint
• Go test

We should implement a few convenience methods in order to reduce the constant use of map[string]interface{}{"":...}

We can include type Fields map[string]interface{} to add a map of details or a WithDetail method which takes in (string, struct) for adding a single detail in a less verbose way.

slog should support convenience methods for entries being included in context.Context structs.

Should follow guidance from Context

Entries currently leverage encoding/json to serialize. We can create a custom serializer that should result in faster performance.

When cloning an entry the details map is not deep copied, resulting in changes to child entries impacting parent entries.

A number of packages allow for including a log.Logger that they'll use. Slog should implement that interface such that it can be used for those.

Log entries created by slog do not currently allow for multiple levels of logging to easily occur.

Examples:

• Adding a label will apply to all future logs from a given entry, even if it's no longer relevant
• Adding a sub-span will require the original span for an entry to need to be rewritten

slog entries should be cloned between usages, which should still have negligible impact.

Enable code scanning via CodeQL

Currently slog will Marshal to a buffer, resulting in potential large allocations. We should just encode directly to the output stream.

Code coverage should be reported via GitHub Action

Dependabot to auto create updates to 'go.mod'

It should be able to create simple configurable cloud clients. e.g.

var (
  spanner = config.Spanner("database", "/projects/test/instances/test/databases/test", "main database")
  topic = config.Topic("topic", "next-step", "topic to notify on completion")
)

Freeform metadata is currently restricted to the labels string to string map. Stackdriver log explorer allows for more operations on non-string types such as comparators on numbers or nested maps. There should be a Details map[string]interface{} to support adding these types.

Use case is to simplify logging and returning of errors:

if err != nil {
  err = fmt.Errorf("wrapping with more details: %w", err)
  slog.Error(err)
  return err
}

to

if err != nil {
  return slog.Errorf("wrapping with more details: %w", err)
}