refactor: Use quote_spanned! strategically in #[program] macro for better error messages

This commit addresses issues #4015 and #3915 by:
- Replacing quote! with quote_spanned! in the #[program] macro where it improves developer UX
- Applying spans to instruction definitions, trait implementations, handler wrappers, CPI methods, and dispatch functions
- Improving CLI error messages to show struct names and accurate line numbers
- Simplifying error handling and removing unnecessary span extractions

Signed-off-by: AvhiMaz <avhimazumder5@outlook.com>

Author: AvhiMaz

CHANGELOG.md

@@ -617,7 +617,7 @@ See the [Anchor 0.29 release notes](https://www.anchor-lang.com/release-notes/0.
 - spl: Re-export the `spl_token` crate ([#1665](https://github.com/coral-xyz/anchor/pull/1665)).
 - lang, cli, spl: Update solana toolchain to v1.9.13 ([#1653](https://github.com/coral-xyz/anchor/pull/1653) and [#1751](https://github.com/coral-xyz/anchor/pull/1751)).
 - lang: `Program` type now deserializes `programdata_address` only on demand ([#1723](https://github.com/coral-xyz/anchor/pull/1723)).
-- ts: Make `Provider` an interface and adjust its signatures and add `AnchorProvider` implementor class ([#1707](https://github.com/coral-xyz/anchor/pull/1707)).
+- ts: Make `Provider` an interface and adjust its signatures and add `AnchorProvider` implementer class ([#1707](https://github.com/coral-xyz/anchor/pull/1707)).
 - spl: Change "to" to "from" in `token::burn` ([#1080](https://github.com/coral-xyz/anchor/pull/1080)).
 
 ## [0.23.0] - 2022-03-20

README.md

@@ -41,7 +41,7 @@ To jump straight to examples, go [here](https://github.com/coral-xyz/anchor/tree
 | `anchor-spl`            | CPI clients for SPL programs on Solana                   | [![crates](https://img.shields.io/crates/v/anchor-spl?color=blue)](https://crates.io/crates/anchor-spl)                          | [![Docs.rs](https://docs.rs/anchor-spl/badge.svg)](https://docs.rs/anchor-spl)                                  |
 | `anchor-client`         | Rust client for Anchor programs                          | [![crates](https://img.shields.io/crates/v/anchor-client?color=blue)](https://crates.io/crates/anchor-client)                    | [![Docs.rs](https://docs.rs/anchor-client/badge.svg)](https://docs.rs/anchor-client)                            |
 | `@coral-xyz/anchor`     | TypeScript client for Anchor programs                    | [![npm](https://img.shields.io/npm/v/@coral-xyz/anchor.svg?color=blue)](https://www.npmjs.com/package/@coral-xyz/anchor)         | [![Docs](https://img.shields.io/badge/docs-typedoc-blue)](https://coral-xyz.github.io/anchor/ts/index.html)     |
-| `@coral-xyz/anchor-cli` | CLI to support building and managing an Anchor workspace | [![npm](https://img.shields.io/npm/v/@coral-xyz/anchor-cli.svg?color=blue)](https://www.npmjs.com/package/@coral-xyz/anchor-cli) | [![Docs](https://img.shields.io/badge/docs-typedoc-blue)](https://coral-xyz.github.io/anchor/cli/commands.html) |
+| `@coral-xyz/anchor-cli` | CLI to support building and managing an Anchor workspace | [![npm](https://img.shields.io/npm/v/@coral-xyz/anchor-cli.svg?color=blue)](https://www.npmjs.com/package/@coral-xyz/anchor-cli) | [![Docs](https://img.shields.io/badge/docs-typedoc-blue)](https://www.anchor-lang.com/docs/references/cli) |
 
 ## Note
 

avm/src/lib.rs

@@ -753,7 +753,7 @@ mod tests {
         let expected = vec![version];
         assert_eq!(read_installed_versions().unwrap(), expected);
 
-        // Should ignore this file because its not anchor- prefixed
+        // Should ignore this file because it's not anchor- prefixed
         fs::File::create(AVM_HOME.join("bin").join("garbage").as_path()).unwrap();
         assert_eq!(read_installed_versions().unwrap(), expected);
     }

client/src/lib.rs

@@ -1,4 +1,4 @@
-#![cfg_attr(docsrs, feature(doc_auto_cfg))]
+#![cfg_attr(docsrs, feature(doc_cfg))]
 
 //! An RPC client to interact with Solana programs written in [`anchor_lang`].
 //!

docs/content/docs/basics/cpi.mdx

@@ -6,7 +6,7 @@ description:
 ---
 
 Cross Program Invocations (CPI) refer to the process of one program invoking
-instructions of another program, which enables the composibility of Solana
+instructions of another program, which enables the composability of Solana
 programs.
 
 This section will cover the basics of implementing CPIs in an Anchor program,
@@ -98,7 +98,7 @@ resulting in a successful SOL transfer.
 
 Cross Program Invocations (CPIs) allow one program to invoke instructions on
 another program. The process of implementing a CPI is the same as that of
-creating a instruction where you must specify:
+creating an instruction where you must specify:
 
 1. The program ID of the program being called
 2. The accounts required by the instruction

docs/content/docs/installation.mdx

@@ -468,7 +468,7 @@ To verify that the installation was successful, check the Yarn version:
 yarn --version
 ```
 
-You should the following output:
+You should see the following output:
 
 ```
 1.22.1
@@ -567,7 +567,7 @@ Keypair Path: /Users/test/.config/solana/id.json
 Commitment: confirmed
 ```
 
-The RPC URL and Websocket URL specific the Solana cluster the CLI will make
+The RPC URL and Websocket URL specify the Solana cluster the CLI will make
 requests to. By default this will be mainnet-beta.
 
 You can update the Solana CLI cluster using the following commands:

docs/content/docs/tokens/basics/transfer-tokens.mdx

@@ -303,7 +303,7 @@ describe("token-example", () => {
     console.log("Mint Account", mintAccount);
   });
 
-  it("Mint Tokens", async () => {
+  it("Transfer Tokens", async () => {
     const tx = await program.methods
       .transferTokens()
       .accounts({

docs/content/docs/updates/release-notes/0-31-0.mdx

@@ -102,7 +102,7 @@ Program name: `my-program`
 ### Pass `cargo` args to IDL build
 
 Both `anchor build` and `anchor idl build` commands pass the `cargo` arguments
-to the underyling IDL build command. For example:
+to the underlying IDL build command. For example:
 
 ```
 anchor build -- --features my-feature
@@ -274,7 +274,7 @@ still allows empty discriminators because some non-Anchor programs, e.g. the SPL
 Token program, don't have account discriminators. In that case, safety checks
 should never depend on the discriminator.
 
-Additionally, the IDL generation step also checks whether you have ambigious
+Additionally, the IDL generation step also checks whether you have ambiguous
 discriminators i.e. discriminators that can be used for multiple types. However,
 you should still consider future possibilities, especially when working with
 1-byte discriminators. For example, having an account with discriminator `[1]`
@@ -440,7 +440,7 @@ Building the IDL via the
 [`build_idl`](https://github.com/coral-xyz/anchor/blob/v0.31.0/idl/src/build.rs#L119)
 function made it impossible to extend its functionality e.g. add new parameters
 without a breaking change. To solve this problem, there is a new way to build
-IDLs programatically:
+IDLs programmatically:
 
 ```rs
 let idl = IdlBuilder::new().program_path(path).skip_lint(true).build()?;

lang/attribute/account/src/lazy.rs

@@ -21,7 +21,7 @@ pub fn gen_lazy(strct: &syn::ItemStruct) -> syn::Result<TokenStream> {
     let load_panic_docs = quote! {
         /// # Panics
         ///
-        /// If there is an existing mutable reference crated by any of the `load_mut` methods.
+        /// If there is an existing mutable reference created by any of the `load_mut` methods.
     };
     let load_mut_panic_docs = quote! {
         /// # Panics

lang/attribute/program/src/declare_program/mods/internal.rs

@@ -83,7 +83,7 @@ fn gen_internal_args_mod(idl: &Idl) -> proc_macro2::TokenStream {
         /// An Anchor generated module containing the program's set of instructions, where each
         /// method handler in the `#[program]` mod is associated with a struct defining the input
         /// arguments to the method. These should be used directly, when one wants to serialize
-        /// Anchor instruction data, for example, when specifying instructions instructions on a
+        /// Anchor instruction data, for example, when specifying instructions on a
         /// client.
         pub mod args {
             use super::*;