Mauricio Caceres Bravo

@erciomunoz This is not a `gtools` bug per se, so to the extent it's a bug at all it would be on Stata. As documented in the help files, weights...

@erciomunoz I've decided to leave this issue up in case others have a similar question about how `gegen` and `gcollapse` weights are meant to work. I've changed the title to...

@fredericky123 The current limitation of the Stata plugin API is that I can read strL variables in version 14.1 and later, but I cannot write strL variables at all, so...

@fredericky123 You can code it up as needed. I'm not sure what the general use case is, but encoding, copying the unique levels to a frame, reshaping, then merge (frlink/frget...

@lan-slot It looks like the results are not being shown in monospace; that seems like a setting you could change on the jupyter side? If you don't want monospace, I...

Try `set more off`

@jonathandroth The Stata version is currently about 10x faster but the code-base is significantly different. Before doing a full re-write though I can try optimize the code around the margins...

FYI it's different each run and I'm not sure what's causing the sort order of the saved FEs to change. This also causes `xbd` and `resid` to change, if they...

@sergiocorreia Actually they're just wrong, sorry for the multiple messages: ```stata clear sysuse auto, clear ivreghdfe price (mpg = turn), absorb(a1=rep78) cluster(rep78) ivreghdfe price (mpg = turn), absorb(a2=rep78) cluster(rep78) reghdfe...

I think the trick will be to loop through stata row-wise. Atm I loop through Stata column-wise. It sounds like the performance loss in Arrow will be smaller than the...