Marco Magdy
Marco Magdy
> which I think is much more robust Why do you think so?
I hate to digress this thread further but a) you’re conflating Rust the programming language with the Lambda runtime. b) The C++ Lambda runtime is also under awslabs just like...
bah! my bad. I misunderstood.
> https://github.com/tpope/vim-repeat Yeah. I do have that installed already.
We are actively working on this. We have opened an initial [PR in Envoy's repository](https://github.com/envoyproxy/envoy/pull/10260) for Lambda integration. Once that PR is merged (and a couple other follow up PRs)...
@s-stefanov things are progressing for sure. That PR was only the first one :) we've been working on others and they've been merged as well. We are working on the...
>Because the packager will wrap all of the shared libs needed for your executable including the whole C runtime and standard libraries > ... > But in this manner you...
I agree that if one of your dependencies already exist in the runtime then you shouldn't package it. That applies to libc and others. >what's the point anyway of linking...
If you are asking if it's possible to build a packager that takes a list of libraries as its input and use only those libraries as dependencies together with the...
Also `invocation_response` has a [public constructor](https://github.com/awslabs/aws-lambda-cpp/blob/934d2547fd573ece89ccbdaad2161a7e4d46fd1e/include/aws/lambda-runtime/runtime.h#L100) which you can pass it a payload and whether a success or a failure response.