| 1 |
On 12/06/2020 18:24, Georgy Yakovlev wrote: |
| 2 |
> On 6/12/20 4:16 AM, Luca Barbato wrote: |
| 3 |
>> On 12/06/2020 11:04, Georgy Yakovlev wrote: |
| 4 |
>>> +# cargo_src_configure --no-default-features |
| 5 |
>> |
| 6 |
>> Shall we default in not-defaulting so we can spare some boilerplate? |
| 7 |
> I don't think so. Let me explain. |
| 8 |
> |
| 9 |
> First of all, this will force to explicitly micro-manage all the |
| 10 |
> features for all the packages in the tree. |
| 11 |
> |
| 12 |
|
| 13 |
The idea is: |
| 14 |
- if myfeatures is empty, do not pass --no-default-features. |
| 15 |
- if myfeatures has content, automatically pass --no-default-features. |
| 16 |
|
| 17 |
--no-default-features --features default seems working as intended btw. |
| 18 |
|
| 19 |
lu |
Archives