docs: fix README.md

[murfffi]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @murfffi, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on updating the README.md file to ensure the Go library usage example is current and accurate. The changes reflect a refactoring of the underlying API for downloading DuckDB, providing users with correct code to integrate the library into their projects.

Highlights

• Documentation Update: The Go code example demonstrating library usage in README.md has been updated to reflect recent API changes.
• API Refactoring: The example now uses download.Do(download.DefaultSpec()) instead of the previous getaduck.Download(getaduck.Options{}), indicating a change in the library's interface.
• Code Completeness: The package main declaration has been added to the Go example, making it a complete and runnable snippet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly updates the usage example in the README.md to align with the current library API, making it a runnable and accurate guide for users. My review includes one suggestion to further improve the example code by using more idiomatic error handling.

[gemini-code-assist]

For better error handling in this example, consider using log.Fatal(err) instead of panic(err). log.Fatal is generally preferred for exiting a program from main on an unrecoverable error, as it provides a clean exit without a stack trace. This would also make the example consistent with the error handling in the project's main.go file.

To apply this change, you will also need to add "log" to the import block.

Suggested change

	panic(err)
	log.Fatal(err)