feat: realize_bipartite_degseq() creates a bipartite graph from two degree sequences

[szhorvat]

No description provided.

[aviator-app]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged using Aviator.

---

See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.

[szhorvat]

@krlmlr @maelle I need your help here. I'm not sure how to best deal with this:

> realize_bipartite_degseq(c(1,1), c(2))
Error in match.arg(arg = arg, choices = choices, several.ok = several.ok) : 
  'arg' must be of length 1

This comes from match.args() happening in realize_bipartite_degree_sequence_impl and not in realize_bipartite_degseq. Can you suggest specific code to fix this?

[szhorvat]

I pushed a commit with one possible fix. Let me know if this is the idiomatic way to handle this.

[szhorvat]

@maelle I'm confused about why the pkgdown test fails. The documentation of this function is structured exactly the same way as that of realize_degseq(). What is the difference between them that causes the failure?

[krlmlr]

The repeated argument matching seems like a safe way to handle this, yes.

We need to add this and every other new function to _pkgdown.yml . Some are added automatically via concepts or name patterns:

rigraph/_pkgdown.yml

Lines 39 to 42 in 4875489

	- contents:
	- starts_with("make_")
	- realize_degseq
	- has_concept("deterministic constructors")

[krlmlr]

Thanks!