`#[event(fetch)]` should name the generated function after the input

[jyn514]

This error is confusing:

error[E0428]: the name `fetch` is defined multiple times
  --> rust-sandbox/src/lib.rs:38:1
   |
36 | fn fetch() {}
   | ---------- previous definition of the value `fetch` here
37 | 
38 | #[event(fetch, respond_with_errors)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `fetch` redefined here
   |
   = note: `fetch` must be defined only once in the value namespace of this module
   = note: this error originates in the attribute macro `event` (in Nightly builds, run with -Z macro-backtrace for more info)

It would be better to name the generated function whatever it was originally (in this case, main).

[nilslice]

I believe this one is actually a little more tricky.. we wasm_bindgen the fetch method that is created and wraps the glue code to call your worker entry point.

let wasm_bindgen_code =
                wasm_bindgen_macro_support::expand(TokenStream::new().into(), wrapper_fn)
                    .expect("wasm_bindgen macro failed to expand");

            let output = quote! {
                #input_fn

                #wasm_bindgen_code
            };

The wasm_bindgen_macro_support::expand code would need to support the ability to rename the user-defined function to fetch as it is defined for the eventual JS binding which needs that name. I think it can be done in the attr param to the function... would need to look more closely though.

[zebp]

Unintentionally fixed by #106 by moving the generated function into it's own module.