YR Chen

If you forked a package and thus having the same identity, aren’t these two libraries basically one and the user should choose either of them? > in the practice of...

No, they shouldn’t — these arguments are explicitly set for SwiftPM, and we should clarify this in the description. I would take the functionality of "Run Swift script" to be...

> So if I quickly want to test a new feature, say like regex, which requires command line arguments to run, I have to save a swift file with the...

There’s almost no way to "translate" between SwiftPM and Swift Driver arguments. They have clearly different usage, and, even worse, unstable interface to some extent. It’s impossible for us to...

Note that the demo doesn’t work at the moment because parameterized protocol support is not fully implemented yet. It is valid and hopefully we could use it starting from 5.7.

I believe this could be closed. Swift 5.7 will enable such syntax, but we’re not using closures any more🤷‍♂️

We can drop `context:` from `LambdaHandler`’s initializer, then the `SimpleLambdaHandler` model will just fit (we can keep `async` and `throws` so users can still initialize some resources if they want).

Is there any reason they cannot use async/await for asynchronous startup, and use throw in place of manual termination? I think that's the "simple" way and should work for most...

I agree that this extension should go away... `APIGateway` issue could have a better solution. I'm not saying that I've already got a better solution. I'm just showing how I...

> The existing link to `101.lug.ustc.edu.cn` looks fine to me. (P.S. removing nav items from `mkdocs.yml` does _not_ stop the markdown files from being rendered.) This PR also moves `Specs`...