On Fri, 12 Jun 2020 09:24:11 -0700
Georgy Yakovlev wrote:
> Not sure if --features=default will activate default set and how it
> will react to being passed along.
>
> --no-default-features --features default
> IDK, looks kinda unnatural.
>
> I have a feeling that we'll get more boilerplate
On 6/12/20 11:59 AM, Luca Barbato wrote:
> On 12/06/2020 18:24, Georgy Yakovlev wrote:
>> On 6/12/20 4:16 AM, Luca Barbato wrote:
>>> On 12/06/2020 11:04, Georgy Yakovlev wrote:
+# cargo_src_configure --no-default-features
>>>
>>> Shall we default in not-defaulting so we can spare some
On 12/06/2020 18:24, Georgy Yakovlev wrote:
On 6/12/20 4:16 AM, Luca Barbato wrote:
On 12/06/2020 11:04, Georgy Yakovlev wrote:
+# cargo_src_configure --no-default-features
Shall we default in not-defaulting so we can spare some boilerplate?
I don't think so. Let me explain.
First of
On 6/12/20 6:03 AM, Kent Fredric wrote:
I've replied privately by mistake, replying to the list again.
> On Fri, 12 Jun 2020 02:04:51 -0700
> Georgy Yakovlev wrote:
>
>> +# cargo_src_configure --no-default-features
>
> Looking at the source, I don't see how this is passed from this command
On 6/12/20 4:16 AM, Luca Barbato wrote:
> On 12/06/2020 11:04, Georgy Yakovlev wrote:
>> +# cargo_src_configure --no-default-features
>
> Shall we default in not-defaulting so we can spare some boilerplate?
I don't think so. Let me explain.
First of all, this will force to explicitly
On Fri, 12 Jun 2020 02:04:51 -0700
Georgy Yakovlev wrote:
> +#cargo_src_configure --no-default-features
Looking at the source, I don't see how this is passed from this command to
anything.
> + # transform array from simple feature list
> + # to multiple cargo args:
> + #
On 12/06/2020 11:04, Georgy Yakovlev wrote:
+# cargo_src_configure --no-default-features
Shall we default in not-defaulting so we can spare some boilerplate?
lu
