Last two crates off nightly

[rylev]

No description provided.

[peterhuene]

I think we need to feature-gate the change to remove Diagnostic as without it we get poor error messages from the proc macros.

Before this change:

error: cannot bind to 'nope' because it is not a binding parameter of the function
 --> examples/http/src/functions/greet.rs:5:18
  |
5 | #[binding(name = "nope", auth_level = "anonymous")]
  |                  ^^^^^^

With this change:

error: custom attribute panicked
 --> examples/http/src/functions/greet.rs:4:1
  |
4 | #[func]
  | ^^^^^^^
  |
  = help: message: cannot bind to 'nope' because it is not a binding parameter of the function

[rylev]

@peterhuene The code changes should be well set up to handle feature gating. I tried using cfg-if to handle auto switching between nightly and stable but didn't get it working.

I'll get something working before we merge

[rylev]

@peterhuene This is ready to go I believe. I think the next thing to do is to change the generated cargo project to have a unstable or diagnostics feature which sets the unstable feature on azure-functions and then change the docker file to run cargo with this feature set. I can do that in a separate PR.

[peterhuene]

Thanks @rylev! I'll review this in-depth tonight and hopefully get it merged. I can update the Dockerfile template to enable the unstable feature for cargo func new-app. I plan on finishing the cargo func new command this week, at which point I think it warrants a new release with all these changes.

[peterhuene]

@rylev can you rebase and possibly squash? I should have held off on merging in the dependency updates, sorry about that.

[peterhuene]

foo is a placeholder name that generates a warning for clippy.

Perhaps message instead?

[rylev]

Whoops. How embarrassing!

[peterhuene]

Looks great, just a few feedback changes to make. Awesome work!