Idan Arye

Ideally with #23 you should be able to do something like this (I'm not fixated on the syntax yet): ```rust #[typed_builder::fill_generics( B, generic_param = T, constraints(without(a)), derivatives( O(with(a)), ), )]...

Another option is to support something like this: ```rust #[derive(TypedBuilder)] #[builder( builder_only_generics('a), builder_only_fields( with_a: &'a AWrapper, ), )] struct B { z: u64, #[builder(setter(skip), default = with_a.0)] a: A, b:...

I never tried using it with Django...

This seems to be a limitation of Django and PDB themselves. I found a package that allows using PDB with django without manually adding `pdb.set_trace()`: https://github.com/HassenPy/django-pdb. I checked it with...

Never looked that much into it, since I'm not using Django myself, but I suspect that PDB does not support multithreading.

At least, not unless you call `pdb.set_trace()` manually in the thread you want to debug.

> To keep the `builder()` function as is, there could be a `.context()` function to set the context. So... something like this? ```rust #[derive(TypedBuilder)] #[builder(context(/*Syntax TBD*/))] struct Foo { #[buidler(default...

I really don't want to move the defaults elsewhere. If I have to specify dependencies, I'd rather make a breaking change and do something like this: ```rust #[derive(TypedBuilder)] #[builder(context( x:...

1. Why would you ever need to specifically address the base builder type? I can imagine wanting to write a function that returns the builder with some fields filled in,...

Try running `:VBGtoggleTerminalBuffer` - preferably right after you start the debugger: ```vim :call vebugger#jdb#start('Application', { 'classpath': './target', 'srcpath': './src' }) | VBGtoggleTerminalBuffer ``` What gets written there? Any errors?