You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Xml_iter is very crude and not very used. I would like to both improve the functionality and deprecate the current interface.
We can do that by providing a way to export to lambdasoup. I would prefer to do it while not actually depending on lambdasoup, so some structural thing would be nice.
This would also potentially provide us with a good streaming printer, when one is added to lambdasoup.
The text was updated successfully, but these errors were encountered:
@Drup, Markup.ml has a streaming printer – so Lambda Soup does too, it's the Soup.to_string function. It can also be done with soup |> Soup.signals |> Markup.write_html |> Markup.to_something_other_than_string.... I am not sure what the purpose or use case of Xml_iter is, but depending on what it actually is, can it be achieved by functorizing Lambda Soup over its tree representation somehow?
Currently,
Xml_iter
is very crude and not very used. I would like to both improve the functionality and deprecate the current interface.We can do that by providing a way to export to lambdasoup. I would prefer to do it while not actually depending on lambdasoup, so some structural thing would be nice.
This would also potentially provide us with a good streaming printer, when one is added to lambdasoup.
The text was updated successfully, but these errors were encountered: